[Touch-packages] [Bug 1444958] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From cdead...@us.ibm.com 2016-11-22 02:16 EDT---

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

Title:
  STC830:Brazos:br311p06:  file(s) are deleted from the /tmp after each
  reboot on Ubuntu OS

Status in systemd package in Ubuntu:
  Invalid
Status in systemd package in Debian:
  Fix Released

Bug description:
  == Comment: #0 - Application Cdeadmin  - 2015-04-16 
01:55:24 ==
   State: Open by: mpham on 14 April 2015 14:26:40 

  Problem Description:
  

  File(s) are deleted from the /tmp after each reboot on Ubuntu OS.

  Even after the modification of

  TMPTIME=-1 or infinite or 60 in /etc/default/rcS.

  Symtem Info:
  =

   ver 1.5.4.3 - OS, HTX, Firmware and Machine details

 OS: GNU/Linux
 OS Version: Ubuntu Vivid Vervet (development branch) \n \l
 Kernel Version: 3.19.0-10-generic
HTX Version: htxubuntu-331
  Host Name: br311p06.site
  Machine Serial No: IBM,02109D2E7
 Machine Type/Model: IBM,9119-MHE
System FW Level: FW830.00 (SC830_028)

  HMC:
  =

  brhmc4 (9.3.242.95)
  

  Transferring the defect to Linux team for further analysis.

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

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

[Touch-packages] [Bug 1511824] Re: Can't login as ordinary user with lightdm

[Adumont]

Same bug here, Ubuntu 16.04.1 LTS.

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

Title:
  Can't login as ordinary user with lightdm

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I can't login as ordinary user rose with lightdm.
  It is an Ubuntu 15.04 for armv7l .
  At the beginning I saw the already reported issues with kwallet, which is not 
installed. I commented out the corresponding lines in. I have now:

  root@odroid6:~# cat /etc/pam.d/lightdm
  #%PAM-1.0
  auth requisite pam_nologin.so
  auth sufficient pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  auth optional pam_gnome_keyring.so
  #auth optional pam_kwallet.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  session required pam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optional pam_gnome_keyring.so auto_start
  #session optional pam_kwallet.so auto_start
  session required pam_env.so readenv=1
  session required pam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale
  @include common-password

  and

  root@odroid6:~# cat /etc/pam.d/lightdm-greeter
  #%PAM-1.0
  auth required pam_permit.so
  auth optional pam_gnome_keyring.so
  #auth optional pam_kwallet.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  session required pam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optional pam_gnome_keyring.so auto_start
  #session optional pam_kwallet.so auto_start
  session required pam_env.so readenv=1
  session required pam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale

  It seems that my password is accepted (login via ssh works perfectly),
  but with lightdm I get only a black screen with mouse cursor. Login as
  user odroid which is in group nopasswdlogin with lightdm works.

  After trying to login as user rose, I have to login with ssh and kill
  all processes owned by rose. At the end of /var/log/auth.log I see:

  Oct 28 19:34:17 odroid6 lightdm: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" not met by user "rose"
  Oct 28 19:34:26 odroid6 lightdm: pam_unix(lightdm-greeter:session): session 
closed for user lightdm
  Oct 28 19:34:26 odroid6 lightdm: pam_unix(lightdm:session): session opened 
for user rose by (uid=0)
  Oct 28 19:34:26 odroid6 systemd-logind[651]: New session c8 of user rose.
  Oct 28 19:34:26 odroid6 systemd: pam_unix(systemd-user:session): session 
opened for user rose by (uid=0)
  Oct 28 19:35:10 odroid6 systemd-logind[651]: Removed session c6.
  Oct 28 19:35:10 odroid6 systemd: pam_unix(systemd-user:session): session 
closed for user lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.2-0ubuntu1.1
  Uname: Linux 3.10.82-57 armv7l
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: armhf
  Date: Fri Oct 30 18:14:21 2015
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2015-10-28T17:40:04.609656
  mtime.conffile..etc.pam.d.lightdm.greeter: 2015-10-28T17:53:38.848444

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

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

[Touch-packages] [Bug 1633520] Re: Support dbus runtime relocation

[Launchpad Bug Tracker]

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

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

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

Title:
  Support dbus runtime relocation

Status in D-Bus:
  Unknown
Status in dbus package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  For example, when running in a snap.

  I ran into this while testing a unity8 desktop session snap.  Session
  services were being dbus-activated, but dbus was running the hardcoded
  paths in the session desktop files.  Which weren't pointed into the
  snap.

  DBus has support for relocating those paths, but it only does so on
  Windows.

  I've added a patch to support $DBUS_ROOT on Unix and relocate paths as
  needed.  I've linked the upstream bug here.  We may want to consider
  patching Ubuntu while we wait for it to land upstream.

  I've attached the patch here too.

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

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

[Touch-packages] [Bug 1633520] Re: Support dbus runtime relocation

[Launchpad Bug Tracker]

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

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

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

Title:
  Support dbus runtime relocation

Status in D-Bus:
  Unknown
Status in dbus package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  For example, when running in a snap.

  I ran into this while testing a unity8 desktop session snap.  Session
  services were being dbus-activated, but dbus was running the hardcoded
  paths in the session desktop files.  Which weren't pointed into the
  snap.

  DBus has support for relocating those paths, but it only does so on
  Windows.

  I've added a patch to support $DBUS_ROOT on Unix and relocate paths as
  needed.  I've linked the upstream bug here.  We may want to consider
  patching Ubuntu while we wait for it to land upstream.

  I've attached the patch here too.

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

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

[Touch-packages] [Bug 1636573] Re: xinit flooding syslog

[Michael Stockenhuber]

Same here. on Upgrade to Ubuntu 10.10, syslog is filling up.

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

Title:
  xinit flooding syslog

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows
  (kodi is a media center):

  /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-
  standalone -- :1 -nolisten tcp vt8

  This used to work fine with Ubuntu 16.04, but since the upgrade to
  16.10 lots of log messages are sent to syslog. They are all
  repetitions of the following two lines:

  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.
  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_status() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.

  These messages amount to >200 GB per day, so this is eating up all the
  disk space.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Oct 25 18:41:22 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-06 (1753 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago)

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

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

[Touch-packages] [Bug 1643467] Re: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

[Mozaic]

For information in Firefox 50 release notes:
https://www.mozilla.org/en-US/firefox/50.0/releasenotes/
"Blocked versions of libavcodec older than 54.35.1"

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

Title:
  Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

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

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

[Touch-packages] [Bug 1643777] [NEW] [phone] Enable flight mode, the cellular data indicator still be ON in settings.

[Hannah Zhu]

Public bug reported:

Information:
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 22
device name: turbo
channel: ubuntu-touch/rc/meizu-pd.en
last update: 2016-11-21 16:17:17
version version: 22
version ubuntu: 20161118
version device: 20160824-d33b825
version custom: 20160831-992-8-12

Precondition:
SIM cards inserted.

Step:
1.Go to system settings, and enable flight mode
2.Go to Cellular settings Panel, and check the cellular data indicator.

Actual result:
Enable flight mode, the cellular data indicator still be ON.

Expect result:
The cellular data indicator should be OFF.

Related test case:
https://prod.practitest.com/p/1548/qtest_runs/6921297/edit

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

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

Title:
  [phone] Enable flight mode, the cellular data indicator still be ON in
  settings.

Status in indicator-network package in Ubuntu:
  New

Bug description:
  Information:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 22
  device name: turbo
  channel: ubuntu-touch/rc/meizu-pd.en
  last update: 2016-11-21 16:17:17
  version version: 22
  version ubuntu: 20161118
  version device: 20160824-d33b825
  version custom: 20160831-992-8-12

  Precondition:
  SIM cards inserted.

  Step:
  1.Go to system settings, and enable flight mode
  2.Go to Cellular settings Panel, and check the cellular data indicator.

  Actual result:
  Enable flight mode, the cellular data indicator still be ON.

  Expect result:
  The cellular data indicator should be OFF.

  Related test case:
  https://prod.practitest.com/p/1548/qtest_runs/6921297/edit

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

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

[C Filorux]

The fix is failing in xenial: I have to repeatedly clean up after the
installer, when it complains that it cannot do its work due to disk
space on the tiny /boot partition.  "My disk is full again!"

The bug remains: The automatic update is not considered an unattended
update, since the user is there attending it via an interactive
application (tell me I'm wrong).

-- 
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 1643766] [NEW] not loading apps

[John Rhodes]

Public bug reported:

what the hell is going on i am continually getting internal error this is 
unacceptable and needs to be fixed immediately, fix now, i will not accept 
anything less, i use to be very satified but this upgrade sucks fix it 
or lose a once loyal customer

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-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
Date: Mon Nov 21 23:30:52 2016
DistUpgraded: 2016-09-05 14:05:34,706 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:1587]
InstallationDate: Installed on 2015-10-02 (416 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: ASUSTeK COMPUTER INC. S550CA
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=eb244521-5462-43d9-b71f-cbe24fe6f442 ro vesafb.invalid=1 
plymouth:debug drm.debug=0xe nopat
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-09-05 (77 days ago)
dmi.bios.date: 11/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: S550CA.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: S550CA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS550CA.202:bd11/23/2012:svnASUSTeKCOMPUTERINC.:pnS550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: S550CA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Nov 21 23:23:27 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   13130 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  not loading apps

Status in xorg package in Ubuntu:
  New

Bug description:
  what the hell is going on i am continually getting internal error this is 
unacceptable and needs to be fixed immediately, fix now, i will not accept 
anything less, i use to be very satified but this upgrade sucks fix it 
  or lose a once loyal customer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-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
  Date: Mon Nov 21 23:30:52 2016
  DistUpgraded: 2016-09-05 14:05:34,706 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) 

[Touch-packages] [Bug 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up

[Scott Moser]

Marking this verified.
I booted an instance in gce.


## launch an instance
  project="smoser-00"
  # from gcloud compute images list ubuntu-1604-xenial-v20161115
  img="/ubuntu-os-cloud/ubuntu-1604-xenial-v20161115"
  name="smfoo3"
  zone="us-east1-b"
  mtype="f1-micro"
  gcloud compute "--project=$project" instances create "$name" \
  "--zone=$zone" "--machine-type=$mtype" --network=default \
  "--maintenance-policy=MIGRATE" \
   --image="$img" \
   --boot-disk-size=10 --boot-disk-type=pd-standard \
   "--boot-disk-device-name=$name"

## ssh in
# get htools for saving logs and such
% git clone https://gist.github.com/29ea35a797c0df1fcb6ac875a024efa9.git htools
% sudo ./htools/save-old-data orig-boot
  new instance local: not found
  new instance net  : not found
  reformattable: not found
  disk_setup ran: true
  mounts ran: true
  proc-mounts:
  /etc/fstab:

% sudo ./htools/enable-proposed
deb http://us-east1.gce.archive.ubuntu.com/ubuntu/ xenial-proposed main universe
% sudo apt-get update -qy && sudo apt-get install cloud-init -qy
% dpkg-query --show cloud-init
cloud-init   0.7.8-49-g9e904bb-0ubuntu1~16.04.1

% sudo ./htools/do-reboot clean
cleared /var/lib/cloud
cleared logs
rebooting

# ssh back in
% cat /proc/uptime
29.78 19.66
% journalctl --full --no-pager | grep -i "ordering" || echo no order
no order
% journalctl --full --no-pager | grep -i "break" || echo no break



%

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

Title:
  resolve service in nsswitch.conf adds 25 seconds to failed lookups
  before systemd-resolved is up

Status in cloud-init:
  Fix Committed
Status in D-Bus:
  Unknown
Status in cloud-init package in Ubuntu:
  Fix Released
Status in dbus package in Ubuntu:
  Won't Fix
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact] 
  In cases where cloud-init used dns during early boot and system was
  configured in nsswitch.conf to use systemd-resolvd, the system would
  timeout on dns attempts making system boot terribly slow.

  [Test Case]
  Boot a system on GCE.
  check for WARN in /var/log/messages
  check that time to boot is reasonable (<30 seconds).  In failure case the
  times would be minutes.

  [Regression Potential]
  Changing order in boot can be dangerous.  There is real chance for 
  regression here, but it should be fairly small as xenial does not include
  systemd-resolved usage.  This was first noticed on yakkety where it did.

  [Other Info]
  It seems useful to SRU this in the event that systemd-resolvd is used
  on 16.04 or the case where user upgrades components (admittedly small use
  case).

  === End SRU Template ===


  
  During boot, cloud-init does DNS resolution checks to if particular metadata 
services are available (in order to determine which cloud it is running on).  
These checks happen before systemd-resolved is up[0] and if they resolve 
unsuccessfully they take 25 seconds to complete.

  This has substantial impact on boot time in all contexts, because
  cloud-init attempts to resolve three known-invalid addresses ("does-
  not-exist.example.com.", "example.invalid." and a random string) to
  enable it to detect when it's running in an environment where a DNS
  server will always return some sort of redirect.  As such, we're
  talking a minimum impact of 75 seconds in all environments.  This
  increases when cloud-init is configured to check for multiple
  environments.

  This means that yakkety is consistently taking 2-3 minutes to boot on
  EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
  seconds thereafter in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1629797/+subscriptions

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

[Touch-packages] [Bug 1623798] Re: Apt update search for automatic updates even if told not

[Launchpad Bug Tracker]

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

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

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

Title:
  Apt update search for automatic updates even if told not

Status in unattended-upgrades package in Ubuntu:
  Expired

Bug description:
  In /etc/apt/apt.conf.d/90_mysettings is "APT::Periodic::Update-
  Package-Lists "0";". Software and updates in settings says it will
  never search for updates.

  Still updates is searched for and displayed. Annoying when you are on
  a limited mobile broadband.

  I expect it not to search for updates.

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

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

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

[Touch-packages] [Bug 1643276] Re: lightdm-gtk-greeter segv with unknown config options

[Launchpad Bug Tracker]

** Branch linked: lp:lightdm

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

Title:
  lightdm-gtk-greeter segv with unknown config options

Status in Light Display Manager:
  In Progress
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  It seems that lightdm-gtk-greeter segfaults if you have an unknown
  option in your configuration file.

  Core was generated by `/usr/sbin/lightdm-gtk-greeter'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f0c4fd418a9 in config_load_from_file (config=0x100, 
path=0x23127d0 "/etc/lightdm/lightdm.conf", messages=0x0, error=0x7fff572556b0)
  at configuration.c:106
  106 *messages = g_list_append (*messages, 
g_strdup_printf ("  [%s] contains unknown option %s", group, keys[j]));
  [Current thread is 1 (Thread 0x7f0c51b189c0 (LWP 28281))]
  (gdb) p group
  $1 = (gchar *) 0x2265c10 "LightDM"
  (gdb) p keys[j]
  $2 = (gchar *) 0x21ecd00 "display-setup-script"
  (gdb) p messages
  $3 = (GList **) 0x0
  (gdb) bt
  #0  0x7f0c4fd418a9 in config_load_from_file (config=0x100, 
path=0x23127d0 "/etc/lightdm/lightdm.conf", messages=0x0, error=0x7fff572556b0)
  at configuration.c:106
  #1  0x7f0c4fd41fe6 in config_load_from_standard_locations 
(config=0x100, config_path=0x0, messages=0x0) at configuration.c:241
  #2  0x7f0c4fd3f029 in update_sessions () at session.c:234
  #3  0x7f0c4fd3f0f3 in lightdm_get_sessions () at session.c:269
  #4  0x0040c972 in main ()

  
  So it looks like a NULL message list arg is passed to config_load_from_file() 
while the function expects non-NULL.

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

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

[Touch-packages] [Bug 1643276] Re: lightdm-gtk-greeter segv with unknown config options

[Robert Ancell]

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

** Changed in: lightdm
   Importance: Undecided => Critical

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

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

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

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

Title:
  lightdm-gtk-greeter segv with unknown config options

Status in Light Display Manager:
  In Progress
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  It seems that lightdm-gtk-greeter segfaults if you have an unknown
  option in your configuration file.

  Core was generated by `/usr/sbin/lightdm-gtk-greeter'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f0c4fd418a9 in config_load_from_file (config=0x100, 
path=0x23127d0 "/etc/lightdm/lightdm.conf", messages=0x0, error=0x7fff572556b0)
  at configuration.c:106
  106 *messages = g_list_append (*messages, 
g_strdup_printf ("  [%s] contains unknown option %s", group, keys[j]));
  [Current thread is 1 (Thread 0x7f0c51b189c0 (LWP 28281))]
  (gdb) p group
  $1 = (gchar *) 0x2265c10 "LightDM"
  (gdb) p keys[j]
  $2 = (gchar *) 0x21ecd00 "display-setup-script"
  (gdb) p messages
  $3 = (GList **) 0x0
  (gdb) bt
  #0  0x7f0c4fd418a9 in config_load_from_file (config=0x100, 
path=0x23127d0 "/etc/lightdm/lightdm.conf", messages=0x0, error=0x7fff572556b0)
  at configuration.c:106
  #1  0x7f0c4fd41fe6 in config_load_from_standard_locations 
(config=0x100, config_path=0x0, messages=0x0) at configuration.c:241
  #2  0x7f0c4fd3f029 in update_sessions () at session.c:234
  #3  0x7f0c4fd3f0f3 in lightdm_get_sessions () at session.c:269
  #4  0x0040c972 in main ()

  
  So it looks like a NULL message list arg is passed to config_load_from_file() 
while the function expects non-NULL.

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

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

[Touch-packages] [Bug 478827] Re: openldap database backend back_perl has undefined symbols (aka slapd-perl back-perl)

[Ryan Tandy]

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

** This bug has been marked a duplicate of bug 90812
   perl backend can't use dynamically loaded modules (DBI, POSIX...)

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

Title:
  openldap database backend back_perl has undefined symbols (aka slapd-
  perl back-perl)

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  Error when starting slapd when configured to use the perl backend 
(/etc/init.d/slapd start):
  Starting OpenLDAP: slapd - failed:
  /usr/sbin/slapd: symbol lookup error: /usr/lib/perl/5.10/auto/Fcntl/Fcntl.so: 
undefined symbol: Perl_Istack_sp_ptr

  This may be related to bug #90812

  When start fails, also verified it was not running with ps.
  Removing the "database perl" section allows it to start.

  
  lsb_release -rd
  Description:Ubuntu 9.10
  Release:9.10

  slapd -V
  @(#) $OpenLDAP: slapd 2.4.18 (Sep  8 2009 17:47:22) $
  
buildd@crested:/build/buildd/openldap-2.4.18/debian/build/servers/slapd

  To reproduce:

  Changed to use slapd.conf rather than ldif configs.
  /etc/defaults/slapd :
  SLAPD_CONF=/etc/ldap/slapd.conf
  SLAPD_USER="openldap"
  SLAPD_GROUP="openldap"
  SLAPD_PIDFILE=
  SLAPD_SERVICES="ldap:/// ldapi:/// ldaps:///"
  SLAPD_SENTINEL_FILE=/etc/ldap/noslapd
  SLAPD_OPTIONS=""

  
  My /etc/ldap/slapd.conf:
  moduleload  back_perl
  include /etc/ldap/schema/core.schema
  include /etc/ldap/schema/cosine.schema
  include /etc/ldap/schema/inetorgperson.schema
  loglevel   1320
  pidfile/var/run/slapd/slapd.pid
  argsfile   /var/run/slapd/slapd.args
  password-hash  {SSHA}
  databaseperl   
  suffix "dc=company,dc=com"
  perlModulePath /etc/ldap/perl
  perlModule SampleLDAP

  
  Copied SampleLDAP.pm from source distribution to /etc/ldap/perl/SampleLDAP.pm
  chown'd it to openldap:
  chmod'd it to 750
  opendlap source location:
  openldap-2.4.19/servers/slapd/back-perl/SampleLDAP.pm

  Fixed bug in SampleLDAP.pm on line 52:
  < print {*STDERR}, "$filterStr\n";
  > print {*STDERR} "$filterStr\n";

  [note: attached the SampleLDAP.pm]

  
  Attempt to start service, and receive the error.
  /etc/init.d/slapd start
  Starting OpenLDAP: slapd - failed:
  /usr/sbin/slapd: symbol lookup error: /usr/lib/perl/5.10/auto/Fcntl/Fcntl.so: 
undefined symbol: Perl_Istack_sp_ptr

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Nov  8 15:16:42 2009
  DistroRelease: Ubuntu 9.10
  Package: slapd 2.4.18-0ubuntu1
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-server
  SourcePackage: openldap
  Uname: Linux 2.6.31-14-server x86_64

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

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

[Touch-packages] [Bug 489597] Re: PMI Schema in slapd package can't be added to database

[Ryan Tandy]

Not sure exactly when it changed, but on xenial, the pmi schema seems to
work fine. Tested:

 - adding the provided LDIF directly: ldapadd -H ldapi:// -Y EXTERNAL -f 
/etc/ldap/schema/pmi.ldif
 - including the schema in a slapd.conf file
 - converting pmi.schema to LDIF and adding that to slapd

and all were successful.

Marking fixed.

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

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

Title:
  PMI Schema in slapd package can't be added to database

Status in openldap package in Ubuntu:
  Fix Released

Bug description:
  The PMI scheme that is provided by Ubuntu karmic makes reference to syntax 
definitions, e.g.:
  olcLdapSyntaxes: {2}( 1.3.6.1.4.1.4203.666.11.10.2.6 DESC 'X.509 PMI role 
syntax' ...)

  which are not recognized by openldap. The utility splatest can convert
  the PMI scheme into a LDIF file but when trying to add the ldif
  content to the LDAP database we get an error. The same applies when
  adding the ldif file with slaptest to slapd.d configuration directory
  and then checking the database using slapcat. As an example the out
  put of the ldapadd command is shown:

  $ ldapadd -Y EXTERNAL -H ldapi:/// -f pmi.ldif

  adding new entry "cn={14}pmi,cn=schema,cn=config"
  ldap_add: Other (e.g., implementation specific) error (80)
additional info: olcAttributeTypes: Syntax not found: ""

  
  Finally, the content of the ldif file for completeness:

  dn: cn={14}pmi,cn=schema,cn=config
  objectClass: olcSchemaConfig
  cn: pmi
  olcObjectIdentifier: {0}id-oc-pmiUser 2.5.6.24
  olcObjectIdentifier: {1}id-oc-pmiAA 2.5.6.25
  olcObjectIdentifier: {2}id-oc-pmiSOA 2.5.6.26
  olcObjectIdentifier: {3}id-oc-attCertCRLDistributionPts 2.5.6.27
  olcObjectIdentifier: {4}id-oc-privilegePolicy 2.5.6.32
  olcObjectIdentifier: {5}id-oc-pmiDelegationPath 2.5.6.33
  olcObjectIdentifier: {6}id-oc-protectedPrivilegePolicy 2.5.6.34
  olcObjectIdentifier: {7}id-at-attributeCertificate 2.5.4.58
  olcObjectIdentifier: {8}id-at-attributeCertificateRevocationList 2.5.4.59
  olcObjectIdentifier: {9}id-at-aACertificate 2.5.4.61
  olcObjectIdentifier: {10}id-at-attributeDescriptorCertificate 2.5.4.62
  olcObjectIdentifier: {11}id-at-attributeAuthorityRevocationList 2.5.4.63
  olcObjectIdentifier: {12}id-at-privPolicy 2.5.4.71
  olcObjectIdentifier: {13}id-at-role 2.5.4.72
  olcObjectIdentifier: {14}id-at-delegationPath 2.5.4.73
  olcObjectIdentifier: {15}id-at-protPrivPolicy 2.5.4.74
  olcObjectIdentifier: {16}id-at-xMLPrivilegeInfo 2.5.4.75
  olcObjectIdentifier: {17}id-at-xMLPprotPrivPolicy 2.5.4.76
  olcObjectIdentifier: {18}id-mr 2.5.13
  olcObjectIdentifier: {19}id-mr-attributeCertificateMatch id-mr:42
  olcObjectIdentifier: {20}id-mr-attributeCertificateExactMatch id-mr:45
  olcObjectIdentifier: {21}id-mr-holderIssuerMatch id-mr:46
  olcObjectIdentifier: {22}id-mr-authAttIdMatch id-mr:53
  olcObjectIdentifier: {23}id-mr-roleSpecCertIdMatch id-mr:54
  olcObjectIdentifier: {24}id-mr-basicAttConstraintsMatch id-mr:55
  olcObjectIdentifier: {25}id-mr-delegatedNameConstraintsMatch id-mr:56
  olcObjectIdentifier: {26}id-mr-timeSpecMatch id-mr:57
  olcObjectIdentifier: {27}id-mr-attDescriptorMatch id-mr:58
  olcObjectIdentifier: {28}id-mr-acceptableCertPoliciesMatch id-mr:59
  olcObjectIdentifier: {29}id-mr-delegationPathMatch id-mr:61
  olcObjectIdentifier: {30}id-mr-sOAIdentifierMatch id-mr:66
  olcObjectIdentifier: {31}id-mr-indirectIssuerMatch id-mr:67
  olcObjectIdentifier: {32}AttributeCertificate 1.3.6.1.4.1.4203.666.11.10.2.1
  olcObjectIdentifier: {33}CertificateList 1.3.6.1.4.1.1466.115.121.1.9
  olcObjectIdentifier: {34}AttCertPath 1.3.6.1.4.1.4203.666.11.10.2.4
  olcObjectIdentifier: {35}PolicySyntax 1.3.6.1.4.1.4203.666.11.10.2.5
  olcObjectIdentifier: {36}RoleSyntax 1.3.6.1.4.1.4203.666.11.10.2.6
  olcAttributeTypes: {0}( id-at-role NAME 'role' DESC 'X.509 Role attribute, use
;binary' SYNTAX RoleSyntax )
  olcAttributeTypes: {1}( id-at-xMLPrivilegeInfo NAME 'xmlPrivilegeInfo' DESC 'X
   .509 XML privilege information attribute' SYNTAX 1.3.6.1.4.1.1466.115.121.1.1
   5 )
  olcAttributeTypes: {2}( id-at-attributeCertificate NAME 'attributeCertificateA
   ttribute' DESC 'X.509 Attribute certificate attribute, use ;binary' EQUALITY 
   attributeCertificateExactMatch SYNTAX AttributeCertificate )
  olcAttributeTypes: {3}( id-at-aACertificate NAME 'aACertificate' DESC 'X.509 A
   A certificate attribute, use ;binary' EQUALITY attributeCertificateExactMatch
SYNTAX AttributeCertificate )
  olcAttributeTypes: {4}( id-at-attributeDescriptorCertificate NAME 'attributeDe
   scriptorCertificate' DESC 'X.509 Attribute descriptor certificate attribute, 
   use ;binary' EQUALITY attributeCertificateExactMatch SYNTAX AttributeCertific
   ate )
  olcAttributeTypes: {5}( 

[Touch-packages] [Bug 667597] Re: conf.d directory not a configuration directory

[Ryan Tandy]

** Changed in: openldap (Ubuntu)
 Assignee: Abhishek kumar singh (abhishekkumarsingh-cse) => (unassigned)

** Changed in: openldap (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  conf.d directory not a configuration directory

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

Bug description:
  # cat /etc/issue
  Ubuntu 10.04.1 LTS \n \l

  # apt-cache policy slapd
  slapd:
Installed: 2.4.21-0ubuntu5.3
Candidate: 2.4.21-0ubuntu5.3
Version table:
   *** 2.4.21-0ubuntu5.3 0
  500 ftp://10.1.4.17/ubuntu/ lucid-updates/main Packages
  100 /var/lib/dpkg/status
   2.4.21-0ubuntu5.2 0
  500 ftp://10.1.4.17/ubuntu/ lucid-security/main Packages
   2.4.21-0ubuntu5 0
  500 ftp://10.1.4.17/ubuntu/ lucid/main Packages


  PROBLEM DESCRIPTION:

  The slapd package deploys the cn=config directory
  /etc/ldap/slapd.d/cn=config

  Howard Chu, Chief Architect of the OpenLDAP project has publicly
  stated that the slapd.d directory is a configuration DATABASE and is
  not user-editable[1].

  The placement of this configuration database under /etc/ violates the
  Debian Filesystem Hierarchy Standard v2.3 [2] to which Ubuntu also
  adheres [3].

  This is confusing for administrators migrating to the new cn=config
  and can lead them to editing the database directly, which is not
  documented nor intended.

  
  SUGGESTED FIX:
  * Ensure that slapd creates the configuration database somewhere under 
/var/lib
  * Ensure that the slapd package's postinst does not modify the 
configuration database directly
  * Ensure that the /etc/default/slapd file sets the SLAPD_CONF variable to 
the new location of the configuration database

  
  NOTES:

  This may need to be reported to the upstream Debian maintainers,
  however it is my understanding that lenny still uses slapd.conf (and I
  have not had time to test an unstable/testing box or inspect the
  source package, yet).

  
  [1] http://www.openldap.org/lists/openldap-technical/201009/msg00023.html
  [2] http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html
  [3] 
http://people.canonical.com/~cjwatson/ubuntu-policy/policy.html/ch-opersys.html#s-fhs

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

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

[Touch-packages] [Bug 1472056] Re: ntpd can use stale /var/lib/ntp/ntp.conf.dhcp config

[Bug Watch Updater]

** Changed in: ntp (Debian)
   Status: New => Fix Released

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

Title:
  ntpd can use stale /var/lib/ntp/ntp.conf.dhcp config

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  Today, I noticed that my laptop's time was ~4s ahead of my home NTP
  server. Looking at 'ntpdc -sn localhost' I noticed that my laptop was
  trying to sync with an unknown and unreachable server. Surprisingly,
  this server was not in /etc/ntp.conf.

  After some debugging, I found a stale /var/lib/ntp/ntp.conf.dhcp file
  that was several days old. This explains why my clock drift so much as
  I was not sync'ing with any reachable server.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.3
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Mon Jul  6 22:27:52 2015
  InstallationDate: Installed on 2014-01-26 (526 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  KernLog:
   Jul  6 07:42:09 simon-laptop kernel: [116085.154414] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
   Jul  6 07:42:09 simon-laptop kernel: [116085.157431] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
   Jul  6 12:07:27 simon-laptop kernel: [132003.862223] type=1400 
audit(1436198847.026:183): apparmor="DENIED" operation="connect" 
profile="/usr/lib{,32,64}/libreoffice/program/oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_9c6cceebd9df6af8f450bf52b6de65d0" 
pid=30017 comm="oosplash" requested_mask="rw" denied_mask="rw" fsuid=1000 
ouid=1000
   Jul  6 19:54:12 simon-laptop kernel: [153828.256900] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
   Jul  6 19:54:12 simon-laptop kernel: [153828.259982] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
  NtpStatus:
   remote   refid  st t when poll reach   delay   offset  jitter
   
==
ntp.sdeziel.inf 206.108.0.1322 u   37   6415.967  -34.563   
0.000
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.ntp: [modified]
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.init.d.ntp: 2015-07-06T22:27:26.297288
  mtime.conffile..etc.ntp.conf: 2015-07-06T22:24:58.208193

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

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

[Touch-packages] [Bug 1643746] [NEW] Logitech M570 left button doesn't register

[Van Smith]

Public bug reported:

The left mouse button on the Logitech M570 does not register. I have
tried a second M570 and the problem reproduces.  The problem reproduces
with a Logitech wireless mouse.  The problem does NOT reproduce with a
generic wireless mouse.  Solaar is installed.

Clicking the left button repeatedly will eventually result in a left-
click event.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Nov 21 20:51:05 2016
InstallationDate: Installed on 2016-04-10 (225 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2016-10-26 (26 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Logitech M570 left button doesn't register

Status in xorg package in Ubuntu:
  New

Bug description:
  The left mouse button on the Logitech M570 does not register. I have
  tried a second M570 and the problem reproduces.  The problem
  reproduces with a Logitech wireless mouse.  The problem does NOT
  reproduce with a generic wireless mouse.  Solaar is installed.

  Clicking the left button repeatedly will eventually result in a left-
  click event.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Nov 21 20:51:05 2016
  InstallationDate: Installed on 2016-04-10 (225 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (26 days ago)

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

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

[LaMont Jones]

open-iscsi is verified for xenial and yakkety

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

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

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

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  In Progress
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  In Progress
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  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
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) 

  
  [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 1643737] [NEW] Network Manager doesn't use 802.1x password entered in GUI

[StuS]

Public bug reported:

This is a bug that seems to constantly re-surface across multiple
versions in Ubuntu, and I've seen it in other distributions as well.

Scenario:
  I want to enable 802.1x on a wired (*not* wireless), ethernet connection. I 
enter my identity, my computer cert, my ca cert, my private key file, and my 
password for my private key. 

What doesn't work:
I confirm the password works by using openssl. NetworkManager does not save the 
password. When I am asked to re-enter it, the connection fails. I look in 
syslog, and it complains about the private key password being blank.

Workaround:
Open the file:

/etc/NetworkManager/system-connections/[Your network connection]
Example:
$> vim /etc/NetworkManager/system-connections/Wired\ connection\ 1

Add the field:
private-key-password=[your password]

Example:
private-key-password=UtterlyPointlessGloballyReadableStoredInPlaintextPassword

Save the file.

Attempt to re-connect. (and it worked for me).
Look in Network Manager UI, the password seems to now be stored.

Expected behavior:
Entering the password in the GUI works (i.e, it is saved to the file, or at 
least used temporarily when connecting, either way - the latter would be more 
secure)

Additionally, this whole thing is pretty lame, because Network Manager
restricts you to using an encrypted private key, but this is dumb,
because the password is then stored in a globally readable file in
plaintext. Or you can decide to not save a password, and enter every
time in a gui that fails to use the password you type in.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 21 17:52:44 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-11-21 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 10.0.50.1 dev eno1  proto static  metric 100 
 10.0.50.0/23 dev eno1  proto kernel  scope link  src 10.0.50.207  metric 100 
 10.0.254.32 via 10.0.50.1 dev eno1  proto dhcp  metric 100 
 169.254.0.0/16 dev eno1  scope link  metric 1000
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
 Wired connection 1  fcbffec0-f9e4-4405-acfa-1cd80dec7362  802-3-ethernet  
1479779500  Mon 21 Nov 2016 05:51:40 PM PST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 eno1ethernet  connected  /org/freedesktop/NetworkManager/Devices/0  Wired 
connection 1  fcbffec0-f9e4-4405-acfa-1cd80dec7362  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

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

Title:
  Network Manager doesn't use 802.1x password entered in GUI

Status in network-manager package in Ubuntu:
  New

Bug description:
  This is a bug that seems to constantly re-surface across multiple
  versions in Ubuntu, and I've seen it in other distributions as well.

  Scenario:
I want to enable 802.1x on a wired (*not* wireless), ethernet connection. I 
enter my identity, my computer cert, my ca cert, my private key file, and my 
password for my private key. 

  What doesn't work:
  I confirm the password works by using openssl. NetworkManager does not save 
the password. When I am asked to re-enter it, the connection fails. I look in 
syslog, and it complains about the private key password being blank.

  Workaround:

[Touch-packages] [Bug 1606418] Re: PointerConfinement.test_we_update_our_confined_region_on_a_resize

[Launchpad Bug Tracker]

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

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

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

Title:
  PointerConfinement.test_we_update_our_confined_region_on_a_resize

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Randomly fails 1/100 times.
  
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1612/console

  Looking into it, most likely a race with surface resize...

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

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

[Touch-packages] [Bug 1606418] Re: PointerConfinement.test_we_update_our_confined_region_on_a_resize

[Daniel van Vugt]

Reopened because it's still happening (bug 1643627)

** Changed in: mir
   Status: Fix Committed => Confirmed

** Changed in: mir
Milestone: 0.25.0 => None

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

Title:
  PointerConfinement.test_we_update_our_confined_region_on_a_resize

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Randomly fails 1/100 times.
  
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1612/console

  Looking into it, most likely a race with surface resize...

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

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

[Touch-packages] [Bug 1642272] Re: Incorrect UI scale on high-resolution desktop (everything is gigantic)

[Daniel van Vugt]

** Summary changed:

- incorrect UI scale on high-resolution desktop
+ Incorrect UI scale on high-resolution desktop (everything is gigantic)

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

Title:
  Incorrect UI scale on high-resolution desktop (everything is gigantic)

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

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 1214066] Re: phoronix benchmarks on nouveau is 4 times slower today than it was last thursday

[Daniel van Vugt]

Won't fix. Due to lack of activity. The original reporter and the
assignee are both no longer with us. And even the bug title is relative
to "last Thursday" which was back in 2013.

** Changed in: xorg (Ubuntu)
   Status: Fix Committed => Won't Fix

** Changed in: xorg (Ubuntu)
 Assignee: Maarten Lankhorst (mlankhorst) => (unassigned)

** Changed in: xorg (Ubuntu)
   Status: Won't Fix => Invalid

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

Title:
  phoronix benchmarks on nouveau is 4 times slower today than it was
  last thursday

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Description
  phoronix benchmarks on nouveau is 4 times slower today than it was last 
thursday

  * this is with both xmir and plain xorg

  steps:
  1. install saucy from 20130815 on system using nvidia card (I am using two 
different systems nvidia gt640 and  nvidia gt440)
  2. sudo apt-get install phoronix-test-suite
  3 phoronix-test-suite install openarena
  4 phoronix-test-suite run openarena
  5. install saucy from 20130819
  6. sudo apt-get install phoronix-test-suite
  7 phoronix-test-suite install openarena
  8 phoronix-test-suite run openarena

  expected results
  test results from 20130819 image are about the same or better than 20130815 
image

  actual results:
  test results from 20130819 image are about 4 times worse

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Aug 19 17:49:00 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:838a]
  InstallationDate: Installed on 2013-08-19 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130818)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic 
root=UUID=47d5d3bb-9722-4bd4-8d63-e13352d65c1a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.6-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.6-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu3
  xserver.bootTime: Mon Aug 19 16:39:23 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputRaritan D2CIM-DVUSB  KEYBOARD, id 8
   inputRaritan D2CIM-DVUSB  MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.2.901-2ubuntu1
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

[Steve Langasek]

This patch is included in krb5 1.15~beta1-1, which is in zesty-proposed
currently and should reach zesty soon.

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

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

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

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

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

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

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

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Incomplete
Status in krb5 source package in Xenial:
  Incomplete
Status in krb5 source package in Yakkety:
  Incomplete

Bug description:
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

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

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

[Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

[Steve Langasek]

Hi Joshua,

To SRU this into stable releases, we would need a test case for the
problem.  Can you provide an easy-to-follow reproducer that lets us
verify this bug?

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  New

Bug description:
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

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

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

[Touch-packages] [Bug 1643726] [NEW] Invalid option (-p), and man page for passwd does not contain -p option

[PaulSchulz]

Public bug reported:

When unlocking a user account (which doesn't have a password) with
'passwd' I get the message:

  passwd: unlocking the password would result in a passwordless account.
  You should set a password with usermod -p to unlock the password of this 
account.

The Man page for passwd does not describe the '-p' option.

If I try to use -p as an option,I get an unknown option error:

  passwd: invalid option -- 'p'
  Usage: passwd [options] [LOGIN]
  ...

This is in Ubuntu 16.04, source: shadow

Package: passwd
Priority: required
Section: admin
Installed-Size: 2363
Maintainer: Ubuntu Developers 
Original-Maintainer: Shadow package maintainers 

Architecture: amd64
Source: shadow
Version: 1:4.2-3.1ubuntu5
Replaces: manpages-tr (<< 1.0.5), manpages-zh (<< 1.5.1-1)
Depends: libaudit1 (>= 1:2.2.1), libc6 (>= 2.14), libpam0g (>= 0.99.7.1), 
libselinux1 (>= 1.32), libsemanage1 (>= 2.0.3), lsb-base (>= 
4.1+Debian11ubuntu7), libpam-modules, debianutils (>= 2.15.2)
Filename: pool/main/s/shadow/passwd_4.2-3.1ubuntu5_amd64.deb
Size: 779644
MD5sum: d63ef1119cfdf76850618732a0320841
SHA1: 6a53cced36ce2ef45f1ed5c23321736f1d5adcfd
SHA256: 8f1cf17e3d04044156d892db3dddb97cd6753c1d7d74aadd11ba2ddfd5ee2592
Description-en_AU: change and administer password and group data
 This package includes passwd, chsh, chfn, and many other programs to
 maintain password and group data.
 .
 Shadow passwords are supported.  See /usr/share/doc/passwd/README.Debian
Description-md5: 5bbd70e421ed3367a8299e53bd7afed4
Multi-Arch: foreign
Homepage: http://pkg-shadow.alioth.debian.org/
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Supported: 5y
Task: minimal

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

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

Title:
  Invalid option (-p),  and man page for passwd does not contain -p
  option

Status in shadow package in Ubuntu:
  New

Bug description:
  When unlocking a user account (which doesn't have a password) with
  'passwd' I get the message:

passwd: unlocking the password would result in a passwordless account.
You should set a password with usermod -p to unlock the password of this 
account.

  The Man page for passwd does not describe the '-p' option.

  If I try to use -p as an option,I get an unknown option error:

passwd: invalid option -- 'p'
Usage: passwd [options] [LOGIN]
...

  This is in Ubuntu 16.04, source: shadow

  Package: passwd
  Priority: required
  Section: admin
  Installed-Size: 2363
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Shadow package maintainers 

  Architecture: amd64
  Source: shadow
  Version: 1:4.2-3.1ubuntu5
  Replaces: manpages-tr (<< 1.0.5), manpages-zh (<< 1.5.1-1)
  Depends: libaudit1 (>= 1:2.2.1), libc6 (>= 2.14), libpam0g (>= 0.99.7.1), 
libselinux1 (>= 1.32), libsemanage1 (>= 2.0.3), lsb-base (>= 
4.1+Debian11ubuntu7), libpam-modules, debianutils (>= 2.15.2)
  Filename: pool/main/s/shadow/passwd_4.2-3.1ubuntu5_amd64.deb
  Size: 779644
  MD5sum: d63ef1119cfdf76850618732a0320841
  SHA1: 6a53cced36ce2ef45f1ed5c23321736f1d5adcfd
  SHA256: 8f1cf17e3d04044156d892db3dddb97cd6753c1d7d74aadd11ba2ddfd5ee2592
  Description-en_AU: change and administer password and group data
   This package includes passwd, chsh, chfn, and many other programs to
   maintain password and group data.
   .
   Shadow passwords are supported.  See /usr/share/doc/passwd/README.Debian
  Description-md5: 5bbd70e421ed3367a8299e53bd7afed4
  Multi-Arch: foreign
  Homepage: http://pkg-shadow.alioth.debian.org/
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Origin: Ubuntu
  Supported: 5y
  Task: minimal

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

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

[Touch-packages] [Bug 1599301] Re: GenericScopeView test getting stuck

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20161116.1-0ubuntu1

---
unity8 (8.15+17.04.20161116.1-0ubuntu1) zesty; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * MenuItemFactory: bind calendar backend properties to calendarMenu item

Adds support for showing the calendar at the requested date, marking days
with events properly and toggling the visibility of the week number.

  * MenuItemFactory: use Menus.RadioMenu and Menus.ButtonMenu

  * Bump version as USC breaks with unity8 << 8.14

  [ Albert Astals Cid ]
  * [Hopefully] Fix infinite loop in some of the GSV tests (LP:
#1599301)

  [ Marco Trevisan (Treviño) ]
  * testLauncher: use tryCompare to check launcher contentY

  [ Michael Zanetti ]
  * Stabilize OrientedShell tests

 -- Marco Trevisan (Treviño)   Wed, 16 Nov 2016 10:44:59
+

** Changed in: unity8 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  GenericScopeView test getting stuck

Status in qtdeclarative-opensource-src package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Every once in a while britney comes back with a failed run that is, in
  fact, a timed out run. Every time it gets stuck on GenericScopeView -
  but on different tests.

  Here's an example log.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/u/unity8/20160705_203355@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160705-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul  5 23:25:40 2016
  InstallationDate: Installed on 2016-05-06 (60 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/ubuntu/+source/qtdeclarative-opensource-src/+bug/1599301/+subscriptions

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

[Touch-packages] [Bug 1638689] Re: package libnss3 2:3.23-0ubuntu0.14.04.1 [modified: usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/l

[Seth Arnold]

Nish, the trouble with this bug is these lines:

DuplicateSignature: package:libnss3:2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libnss3/changelog.Debian.gz', which is different from other 
instances of package libnss3:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libnss3/changelog.Debian.gz', which is different from other 
instances of package libnss3:i386

This happens a lot more often than you'd suspect -- I don't know why so
many users have both i386 and amd64 versions of packages installed, nor
why they would get updates for these packages out-of-sync like this.
(After all, we publish updates for all arches simultaneously, unless an
oddball arch like s390 or ppc64el or armhf just plain can't build the
fixes.. it's rare.)

Thanks

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

Title:
  package libnss3 2:3.23-0ubuntu0.14.04.1 [modified:
  usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libnss3/changelog.Debian.gz', which is different from
  other instances of package libnss3:i386

Status in nss package in Ubuntu:
  Incomplete

Bug description:
  sudo aptitude upgrade
  ...
  Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.15) over (1.0.1ubuntu2.14) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libnss3_2%3a3.23-0ubuntu0.14.04.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up libapt-pkg4.12:amd64 (1.0.1ubuntu2.15) ...
  Setting up libnspr4:i386 (2:4.12-0ubuntu0.14.04.1) ...
  dpkg: dependency problems prevent configuration of libnss3-1d:i386:
   libnss3-1d:i386 depends on libnss3 (= 2:3.23-0ubuntu0.14.04.1); however:
Version of libnss3:i386 on system is 2:3.16.3-1ubuntu1.

  dpkg: error processing package libnss3-1d:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: error processing package libnss3:amd64 (--configure):
   package libnss3:amd64 2:3.23-0ubuntu0.14.04.1 cannot be configured because 
libnss3:i386 is at a different version (2:3.16.3-1ubuntu1)
  dpkg: error processing package libnss3:i386 (--configure):
   package libnss3:i386 2:3.16.3-1ubuntu1 cannot be configured because 
libnss3:amd64 is at a different version (2:3.23-0ubuntu0.14.04.1)
  dpkg: dependency problems prevent configuration of libnss3-nssdb:
   libnss3-nssdb depends on libnss3 (= 2:3.23-0ubuntu0.14.04.1); however:
Package libnss3:amd64 is not configured yet.

  dpkg: error processing package libnss3-nssdb (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
  Errors were encountered while processing:
   libnss3-1d:i386
   libnss3:amd64
   libnss3:i386
   libnss3-nssdb

  
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libnss3 2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-68-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Wed Nov  2 12:32:54 2016
  DuplicateSignature: package:libnss3:2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libnss3/changelog.Debian.gz', which is different from other 
instances of package libnss3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libnss3/changelog.Debian.gz', which is different from other 
instances of package libnss3:i386
  InstallationDate: Installed on 2015-09-22 (407 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: nss
  Title: package libnss3 2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libnss3/changelog.Debian.gz', which is 
different from other instances of package libnss3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1641719] Re: Opacity for weekend days same as for other days

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings-components -
0.11+17.04.20161116.1-0ubuntu1

---
ubuntu-settings-components (0.11+17.04.20161116.1-0ubuntu1) zesty; 
urgency=medium

  * Menus: add Pointer and Touch styles to be used depending on the user
interaction with components

Menu items now have a new Style property that defines some common properties
such as shared colors and sizes that change depending on the UX journey. I'm
only defining Pointer and TouchStyles for now, but they can be easily
overridden in case.

Removed some deprecated properties and adapted colors and sizes to new
style.

  * Bump package version as there's a new API for various components
  * Calendar: update to new style with weekdays header and Month
selection (LP: #1640936, #1641719, #1641721, #1641722, #1641724,
#1641728)
  * RadioMenu: add menu item for creating radio items

 -- Marco Trevisan (Treviño)   Wed, 16 Nov 2016 18:54:00
+

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

Title:
  Opacity for weekend days same as for other days

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

Bug description:
  bq M10 rc-proposed silo #2195

  When I pull down the calendar indicator, I see the opacity (or maybe color) 
for weekend days is different than for other work days. But when I switch to 
next month, the opacity is the same for all days.
  Please see short video with this and other bugs with this silo: 
https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641721] Re: Tapping on a day near to the screen edge switches to the next month

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings-components -
0.11+17.04.20161116.1-0ubuntu1

---
ubuntu-settings-components (0.11+17.04.20161116.1-0ubuntu1) zesty; 
urgency=medium

  * Menus: add Pointer and Touch styles to be used depending on the user
interaction with components

Menu items now have a new Style property that defines some common properties
such as shared colors and sizes that change depending on the UX journey. I'm
only defining Pointer and TouchStyles for now, but they can be easily
overridden in case.

Removed some deprecated properties and adapted colors and sizes to new
style.

  * Bump package version as there's a new API for various components
  * Calendar: update to new style with weekdays header and Month
selection (LP: #1640936, #1641719, #1641721, #1641722, #1641724,
#1641728)
  * RadioMenu: add menu item for creating radio items

 -- Marco Trevisan (Treviño)   Wed, 16 Nov 2016 18:54:00
+

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

Title:
  Tapping on a day near to the screen edge switches to the next month

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

Bug description:
  bq M10 rc-proposed silo #2195

  Many times when testing after clicking a day on the right hand side
  (Sundays in my case), the view switched to the next month.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641722] Re: Tapping a day often results in selecting not the day I wanted to

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings-components -
0.11+17.04.20161116.1-0ubuntu1

---
ubuntu-settings-components (0.11+17.04.20161116.1-0ubuntu1) zesty; 
urgency=medium

  * Menus: add Pointer and Touch styles to be used depending on the user
interaction with components

Menu items now have a new Style property that defines some common properties
such as shared colors and sizes that change depending on the UX journey. I'm
only defining Pointer and TouchStyles for now, but they can be easily
overridden in case.

Removed some deprecated properties and adapted colors and sizes to new
style.

  * Bump package version as there's a new API for various components
  * Calendar: update to new style with weekdays header and Month
selection (LP: #1640936, #1641719, #1641721, #1641722, #1641724,
#1641728)
  * RadioMenu: add menu item for creating radio items

 -- Marco Trevisan (Treviño)   Wed, 16 Nov 2016 18:54:00
+

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

Title:
  Tapping a day often results in selecting not the day I wanted to

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

Bug description:
  bq M10 rc-proposed silo #2195

  Many times when testing after tapping a day I ended up selecting a day
  which was below or above the day I was aiming for.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641724] Re: Tapping the month name has no effect

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings-components -
0.11+17.04.20161116.1-0ubuntu1

---
ubuntu-settings-components (0.11+17.04.20161116.1-0ubuntu1) zesty; 
urgency=medium

  * Menus: add Pointer and Touch styles to be used depending on the user
interaction with components

Menu items now have a new Style property that defines some common properties
such as shared colors and sizes that change depending on the UX journey. I'm
only defining Pointer and TouchStyles for now, but they can be easily
overridden in case.

Removed some deprecated properties and adapted colors and sizes to new
style.

  * Bump package version as there's a new API for various components
  * Calendar: update to new style with weekdays header and Month
selection (LP: #1640936, #1641719, #1641721, #1641722, #1641724,
#1641728)
  * RadioMenu: add menu item for creating radio items

 -- Marco Trevisan (Treviño)   Wed, 16 Nov 2016 18:54:00
+

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

Title:
  Tapping the month name has no effect

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

Bug description:
  bq M10 rc-proposed silo #2195

  I would expect that tapping the month name would display events for
  that month. Unfortunately the month name is not clickable.

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

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

[Touch-packages] [Bug 1641728] Re: Tapping a day to unselect it shows more events than was there before

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings-components -
0.11+17.04.20161116.1-0ubuntu1

---
ubuntu-settings-components (0.11+17.04.20161116.1-0ubuntu1) zesty; 
urgency=medium

  * Menus: add Pointer and Touch styles to be used depending on the user
interaction with components

Menu items now have a new Style property that defines some common properties
such as shared colors and sizes that change depending on the UX journey. I'm
only defining Pointer and TouchStyles for now, but they can be easily
overridden in case.

Removed some deprecated properties and adapted colors and sizes to new
style.

  * Bump package version as there's a new API for various components
  * Calendar: update to new style with weekdays header and Month
selection (LP: #1640936, #1641719, #1641721, #1641722, #1641724,
#1641728)
  * RadioMenu: add menu item for creating radio items

 -- Marco Trevisan (Treviño)   Wed, 16 Nov 2016 18:54:00
+

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

Title:
  Tapping a day to unselect it shows more events than was there before

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

Bug description:
  bq M10 rc-proposed silo #2195

  I tap a day to see events related to day day, the day is selected
  (color changed to blue). Then I tap that day again to 'unselect' it.
  The list of events is longer than was before tapping that day in the
  first place.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1643717] [NEW] package tar 1.27.1-1ubuntu0.1 failed to install/upgrade

[Jared Kibele]

Public bug reported:

I'm new to bug reporting so please forgive me if I'm doing it wrong. I
was trying to run apt-get updgrade and it crashed. There appears to be
something wrong with tar, but I don't know what or how. My system is
pretty hosed at the moment.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: tar 1.27.1-1ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39
Uname: Linux 3.13.0-101-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Tue Nov 22 12:14:59 2016
DuplicateSignature: package:tar:1.27.1-1ubuntu0.1:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2014-10-22 (761 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.15
SourcePackage: tar
Title: package tar 1.27.1-1ubuntu0.1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: Upgraded to trusty on 2016-08-07 (106 days ago)

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


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

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

Title:
  package tar 1.27.1-1ubuntu0.1 failed to install/upgrade

Status in tar package in Ubuntu:
  New

Bug description:
  I'm new to bug reporting so please forgive me if I'm doing it wrong. I
  was trying to run apt-get updgrade and it crashed. There appears to be
  something wrong with tar, but I don't know what or how. My system is
  pretty hosed at the moment.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tar 1.27.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-101-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Tue Nov 22 12:14:59 2016
  DuplicateSignature: package:tar:1.27.1-1ubuntu0.1:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-10-22 (761 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: tar
  Title: package tar 1.27.1-1ubuntu0.1 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to trusty on 2016-08-07 (106 days ago)

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

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

[Touch-packages] [Bug 1643222] Re: Merge gdk-pixbuf 2.36.0-1 (main) with Debian unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package gdk-pixbuf - 2.36.0-1ubuntu1

---
gdk-pixbuf (2.36.0-1ubuntu1) zesty; urgency=medium

  * Sync with Debian (LP: #1643222). Remaining change:
- Unset MALLOC_PERTURB_ for the /pixbuf/cve-2015-4491/original test, as
  it fails with OOM, or gets OOM killed.
  * Drop CVE-2016-6352.patch, the fix was applied in new upstream version

 -- Jeremy Bicha   Sat, 19 Nov 2016 12:50:45 -0500

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6352

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

Title:
  Merge gdk-pixbuf 2.36.0-1 (main) with Debian unstable (main)

Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  Please merge gdk-pixbuf 2.36.0-1 (main) with Debian unstable (main)

  This update is needed by gtkm3.0 3.22:
  https://launchpad.net/ubuntu/+source/gtkmm3.0/3.22.0-1/+build/8318

  Explanation of the Ubuntu delta and why it can be dropped:
* SECURITY UPDATE: Fixes for write out-of-bounds error
 - debian/patches/CVE-2016-6352.patch: Be more careful when parsing ico
   headers. Based on upstream patch.
 - CVE-2016-6352

  The patch was backported from 2.35.3 so it's not needed any more

  This change is still needed by the Launchpad builders:
* Merge from Debian unstable (LP: #1573839).  Remaining changes:
  - Unset MALLOC_PERTURB_ for the /pixbuf/cve-2015-4491/original test, as
it fails with OOM, or gets OOM killed.

  Changelog entries since current zesty version 2.34.0-1ubuntu2:

  gdk-pixbuf (2.36.0-1) unstable; urgency=medium

* New upstream release.

   -- Michael Biebl   Mon, 19 Sep 2016 19:10:55 +0200

  gdk-pixbuf (2.35.5-1) unstable; urgency=medium

* New upstream development release.
* Drop 02-tests-Make-sure-to-NULL-terminate-the-arguments-pass.patch, merged
  upstream.
* Bump debhelper compat level to 10.
* Use dh_install --list-missing to show uninstalled files and exclude
  libtool .la files.

   -- Michael Biebl   Tue, 13 Sep 2016 16:17:03 +0200

  gdk-pixbuf (2.35.4-4) unstable; urgency=medium

* Move gtk-doc-tools and libglib2.0-doc from Build-Depends-Indep to
  Build-Depends.

   -- Michael Biebl   Thu, 08 Sep 2016 19:17:54 +0200

  gdk-pixbuf (2.35.4-3) unstable; urgency=medium

* Make sure to NULL terminate the arguments passed to g_test_get_filename().
  Otherwise the /pixbuf/composite2 test will segfault. (Closes: #837030)
* Make test-suite failures fatal again.

   -- Michael Biebl   Thu, 08 Sep 2016 18:59:21 +0200

  gdk-pixbuf (2.35.4-2) unstable; urgency=medium

* Make test-suite failures non-fatal for now to not block ongoing
  transitions.
* Build gtk-doc documentation via --enable-gtk-doc.
* Bump Standards-Version to 3.9.8.

   -- Michael Biebl   Thu, 08 Sep 2016 16:49:06 +0200

  gdk-pixbuf (2.35.4-1) unstable; urgency=medium

* New upstream release.
* Update symbols file with new additions. A few private symbols were
  dropped.
* Use dh-exec for substituting multiarch paths in libgdk-pixbuf2.0-0.install
  and libgdk-pixbuf2.0-dev.links.
* Convert from cdbs to dh.

   -- Michael Biebl   Wed, 07 Sep 2016 18:00:22 +0200

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

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

Re: [Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[David Wonderly]

Using easytether I had a few Hiccup's had to uninstall samba

On Nov 20, 2016 5:30 PM, "Vincent Gerris" <1642...@bugs.launchpad.net>
wrote:

> I noticed a few days back after a failed update that I had cups as a
> broken package.
> I uninstalled and some other packages were removed, then I reinstalled.
> That seemed to work. I don't know what I lost and while reporting I got a
> notification that my conf file was edited.
> Can't remember ever changing anything.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1642796).
> https://bugs.launchpad.net/bugs/1642966
>
> Title:
>   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
>   pre-removal script returned error exit status 1
>
> Status in cups package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This is in xenial-proposed, please block release to -updates
>   accordingly :)
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: cups-daemon 2.1.3-4
>   ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
>   Uname: Linux 4.4.0-46-generic x86_64
>   NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CupsErrorLog:
>
>   Date: Fri Nov 18 11:13:15 2016
>   ErrorMessage: subprocess new pre-removal script returned error exit
> status 1
>   InstallationDate: Installed on 2016-05-02 (200 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%
> 208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-
> 1f08-abcd-d89d67d63461
>   MachineType: Dell Inc. XPS 15 9550
>   Papersize: a4
>   PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups
> 3.16.3
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed
> root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash
> vt.handoff=7
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed
> root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash
> vt.handoff=7
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.1
>apt  1.2.15
>   SourcePackage: cups
>   Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
> new pre-removal script returned error exit status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/07/2016
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 01.02.00
>   dmi.board.name: 0N7TVV
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:
> pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: XPS 15 9550
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions
>

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: 

[Touch-packages] [Bug 1624437] Re: Wish: Provide a gtk/gdk friendly interface to content-hub

[William Hua]

** Branch linked: lp:~attente/content-hub/content-hub-glib-2

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

Title:
  Wish: Provide a gtk/gdk friendly interface to content-hub

Status in content-hub package in Ubuntu:
  In Progress

Bug description:
  There is probably no technical limitation that blocks anyone from
  using the current API of content-hub to implement drag & drop features
  in gdk, but there might be other subtle issues with bringing in qt as
  a dependency to gtk+.

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

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

[Touch-packages] [Bug 1643700] Re: mousetweaks process does not get killed when entering desktop

[Francesco Fumanti]

** Description changed:

  This problem occurs on the current development version of zesty; it does
  not occur on any other Ubuntu version that is currently supported.
  
  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.
  
  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the pointer
  stops moving. It is an accessibility feature for example for people that
  are not able to click with an hardware device, like mouse buttons.
  
  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.
  
  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session.
  
  Here is the terminal output after entering the desktop session:
  
  $ ps -ef | grep mouse
  lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
  frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
  frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse
  
  As you can see, the mousetweaks process started under lightdm is still
- running and there is also a second mousetweaks process that was started
- because the desktop session is configured to automatically start the on-
- screen keyboard Onboard and Onboard is configured to start the hover
- click.
+ running. The second mousetweaks process in the terminal output was
+ started by settings in the desktop session.
  
  This behaviour is new in zesty; in previous Ubuntu versions there was no
  mousetweaks process left running under lightdm after entering the
  desktop session.
  
  As Onboard has not been responsible until now for killing the
  mousetweaks process it started under lightdm, I am filing this bug
  against lightdm.
  
  On the other hand, one could argue that since it is Onboard that starts
- mousetweaks, it is also Onboard's job to kill it when exiting lightdm.
- This is what we from the Onboard development team are wandering now.
+ mousetweaks under lightdm, it is also Onboard's job to kill it when
+ exiting lightdm. This is what we from the Onboard development team are
+ wondering now.
  
  @ lightdm developers or maintainers
  
+ Please let us know, what you think about Onboard being responsible to
+ kill mousetweaks when switching when entering the desktop session.
  
- Please let us know, what you think about it. 
+ I don't know how difficult it will be to implement it, as Onboard cannot
+ simply stop the hover click when it gets killed. In fact, in the desktop
+ session, the hover click can be started independently from Onboard in
+ the Pointing and Clicking tab from the Universal Access control panel in
+ the System Settings.
  
- I am also subscribing marmuta, the main Onboard developer who knows
- about me filing this bug, to this bug thread.
+ I am also subscribing the other members of the Onboard development team
+ to this bug thread.

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

Title:
  mousetweaks process does not get killed when entering desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem occurs on the current development version of zesty; it
  does not occur on any other Ubuntu version that is currently
  supported.

  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.

  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the
  pointer stops moving. It is an accessibility feature for example for
  people that are not able to click with an hardware device, like mouse
  buttons.

  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 

[Touch-packages] [Bug 1641355] Re: libreoffice impress gradients do not work in slide show mode

[Richard Pinnell]

Hi Christopher okay I've done as you suggested, and no problem gradients work 
fine.  I think the problem could be to do with the intel graphics firmware, as 
when I was on 16:10 there was some message about intel firmware (don't recall 
exactly).  I tried to sort that out, but I couldn't get the drivers.  Regards
lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
And intalled Libreoffice 
 apt-cache policy libreoffice
libreoffice:
  Installed: 1:5.2.3~rc2-0ubuntu1~xenial1
  Candidate: 1:5.2.3~rc2-0ubuntu1~xenial1
  Version table:
 *** 1:5.2.3~rc2-0ubuntu1~xenial1 500
500 http://ppa.launchpad.net/libreoffice/libreoffice-5-2/ubuntu 
xenial/main amd64 Packages
100 /var/lib/dpkg/status
 1:5.1.4-0ubuntu1 500
500 http://mx.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
 1:5.1.2-0ubuntu1 500
500 http://mx.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

Title:
  libreoffice  impress gradients do not work in slide show mode

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using libreoffice gradients show up fine in edit mode, but not in the 
slide show.  I have tried downgrading to libreoffice 5.1 using the debs on the 
libreoffice official website but to no avail.  Sometimes the gradients show up 
but distorted on other occasiones the colours do not show at all.   This 
problem started when I upgraded from Lubuntu 16.04 to 16.10.  As I use Impress 
a lot I'm currently downgrading back to 16.04.  Screen shows edit mode.  Looks 
like I can only attach one file I'll attach the sideshow mode screen shot to 
another message.
  apt-cache policy libreoffice
  lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  libreoffice:
Installed: 1:5.2.2-0ubuntu2
Candidate: 1:5.2.2-0ubuntu2
Version table:
   *** 1:5.2.2-0ubuntu2 500
  500 http://mx.archive.ubuntu.com/ubuntu yakkety-updates/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   1:5.2.2-0ubuntu1 500
  500 http://mx.archive.ubuntu.com/ubuntu yakkety/universe amd64 
Packages
   1:5.1.5~rc2-0ubuntu1~yakkety1 500
  500 http://ppa.launchpad.net/libreoffice/libreoffice-5-1/ubuntu 
yakkety/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: LXDE
  Date: Sat Nov 12 16:06:27 2016
  DistUpgraded: 2016-11-04 11:07:52,225 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-27-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics 
Controller [1025:0482]
  InstallationDate: Installed on 2015-11-27 (351 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire 4738
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=b39aa819-f848-41bd-9908-b9e44e6611cd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-11-04 (8 days ago)
  dmi.bios.date: 12/21/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE41_CP
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.12:bd12/21/2010:svnAcer:pnAspire4738:pvrV1.12:rvnAcer:rnJE41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 4738
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Touch-packages] [Bug 1643700] Re: mousetweaks process does not get killed when entering desktop

[Francesco Fumanti]

** Description changed:

  This problem occurs on the current development version of zesty; it does
  not occur on any other Ubuntu version that is currently supported.
  
  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.
  
  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the pointer
  stops moving. It is an accessibility feature for example for people that
  are not able to click with an hardware device, like mouse buttons.
  
  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.
  
  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session.
  
  Here is the terminal output after entering the desktop session:
  
  $ ps -ef | grep mouse
  lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
  frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
  frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse
  
  As you can see, the mousetweaks process started under lightdm is still
  running and there is also a second mousetweaks process that was started
  because the desktop session is configured to automatically start the on-
  screen keyboard Onboard and Onboard is configured to start the hover
  click.
  
  This behaviour is new in zesty; in previous Ubuntu versions there was no
  mousetweaks process left running under lightdm after entering the
- desktop session. Thus, I am filing this as a bug.
+ desktop session.
+ 
+ As Onboard has not been responsible until now for killing the
+ mousetweaks process it started under lightdm, I am filing this bug
+ against lightdm.
+ 
+ On the other hand, one could argue that since it is Onboard that starts
+ mousetweaks, it is also Onboard's job to kill it when exiting lightdm.
+ This is what we from the Onboard development team are wandering now.
+ 
+ @ lightdm developers or maintainers
+ 
+ 
+ Please let us know, what you think about it. 
+ 
+ I am also subscribing marmuta, the main Onboard developer who knows
+ about me filing this bug, to this bug thread.

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

Title:
  mousetweaks process does not get killed when entering desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem occurs on the current development version of zesty; it
  does not occur on any other Ubuntu version that is currently
  supported.

  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.

  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the
  pointer stops moving. It is an accessibility feature for example for
  people that are not able to click with an hardware device, like mouse
  buttons.

  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.

  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session.

  Here is the terminal output after entering the desktop session:

  $ ps -ef | grep mouse
  lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
  frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
  frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse

  As you can see, the mousetweaks process started under lightdm is still
  running and there is also a second mousetweaks process that was
  started because the desktop session is configured to automatically
  start the on-screen keyboard Onboard and Onboard is configured to
  

[Touch-packages] [Bug 1643708] [NEW] Add SPNEGO special case for NTLMSSP+MechListMIC

[Joshua R. Poulson]

Public bug reported:

MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
needs to implement specifically for the NTLMSSP mechanism.  This is
required for compatibility with Windows services.

Upstream commit:
https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

We've run into this issue with Linux to Windows negotiation with
encrypted http using GSSAPI.

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

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  New

Bug description:
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

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

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

[Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

[Joshua R. Poulson]

This is needed for Ubuntu 14.04, 16.04, and 16.10.

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  New

Bug description:
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

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

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

[Touch-packages] [Bug 1635812] Re: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

[Michael Terry]

Thanks for adapting the patch for Ubuntu, Vlad!  I've uploaded to zesty.

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

Title:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

Status in Poppler:
  Unknown
Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: atril 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Oct 22 09:43:08 2016
  ExecutablePath: /usr/bin/atril-thumbnailer
  InstallationDate: Installed on 2016-05-14 (160 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: atril-thumbnailer -s 128 
file:///home/username/Documents/jedi_complaint.pdf 
/tmp/.mate_desktop_thumbnail.8JDPPY
  SegvAnalysis:
   Segfault happened at: 0x7fdcb0258990 : mov
0x50(%rdi),%eax
   PC (0x7fdcb0258990) ok
   source "0x50(%rdi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: atril
  StacktraceTop:
   cmsGetColorSpace () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2
   GfxICCBasedColorSpace::parse(Array*, OutputDev*, GfxState*, int) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   GfxColorSpace::parse(GfxResources*, Object*, OutputDev*, GfxState*, int) () 
from /usr/lib/x86_64-linux-gnu/libpoppler.so.58
   Page::loadThumb(unsigned char**, int*, int*, int*) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
  Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark

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

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

[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

[Pat McGowan]

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

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

Title:
  indicator-datetime uses excessive memory

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

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

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

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

[Touch-packages] [Bug 1643700] Re: mousetweaks process does not get killed when entering desktop

[Francesco Fumanti]

** Description changed:

  This problem occurs on the current development version of zesty; it does
  not occur on any other Ubuntu version that is currently supported.
  
  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.
  
  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the pointer
  stops moving. It is an accessibility feature for example for people that
  are not able to click with an hardware device, like mouse buttons.
  
- Here is how to start the hover click in lightdm: 
- - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right. 
- - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click. 
- - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature. 
+ Here is how to start the hover click in lightdm:
+ - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
+ - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
+ - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.
  
  The problem now is that the mousetweaks process started by Onboard in
- lightdm is still running after entering the desktop session. This was
- not the case in previous Ubuntu versions.
+ lightdm is still running after entering the desktop session.
+ 
+ Here is the terminal output after entering the desktop session:
+ 
+ $ ps -ef | grep mouse
+ lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
+ frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
+ frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse
+ 
+ As you can see, the mousetweaks process started under lightdm is still
+ running and there is also a second mousetweaks process that was started
+ because the desktop session is configured to automatically start the on-
+ screen keyboard Onboard and Onboard is configured to start the hover
+ click.
+ 
+ This behaviour is new in zesty; in previous Ubuntu versions there was no
+ mousetweaks process left running under lightdm after entering the
+ desktop session. Thus, I am filing this as a bug.

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

Title:
  mousetweaks process does not get killed when entering desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem occurs on the current development version of zesty; it
  does not occur on any other Ubuntu version that is currently
  supported.

  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.

  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the
  pointer stops moving. It is an accessibility feature for example for
  people that are not able to click with an hardware device, like mouse
  buttons.

  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.

  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session.

  Here is the terminal output after entering the desktop session:

  $ ps -ef | grep mouse
  lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
  frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
  frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse

  As you can see, the mousetweaks process started under lightdm is still
  running and there is also a second mousetweaks process that was
  started because the desktop session is configured to 

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Chris Osgood]

Seeing a similar issue here with so called "diskless" clients. That is,
all of their filesystems are network mounts including the root
filesystem. These systems use iscsi targets for the root filesystem and
during shutdown the network is turned off before the file I/O operations
are completed which causes the system to hang with filesystem IO errors.

I'm currently looking to see if there is some way to make systemd keep
the network up no matter what, all the way until the machine physically
reboots or shuts down (ie. disable the network shutdown completely).

This worked in 14.04 and got broken in 16.04 apparently due to the
switch to systemd as far as I can tell (great tool, isn't it?).

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Bug 1643700] [NEW] mousetweaks process does not get killed when entering desktop

[Francesco Fumanti]

Public bug reported:

This problem occurs on the current development version of zesty; it does
not occur on any other Ubuntu version that is currently supported.

Lightdm offers the possibility to start the default on-screen keyboard
Onboard. Further, Onboard offers the possibility to start the hover
click, which is provided by a process called mousetweaks.

The hover click consists in having the system automatically perform a
left click (and optionally other click types) shortly after the pointer
stops moving. It is an accessibility feature for example for people that
are not able to click with an hardware device, like mouse buttons.

Here is how to start the hover click in lightdm: 
- Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right. 
- Click on the key on the at the right of the Onboard layout that has a pointer 
as label; an additional column with keys will appear; these are the keys to 
control the hover click. 
- Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature. 

The problem now is that the mousetweaks process started by Onboard in
lightdm is still running after entering the desktop session. This was
not the case in previous Ubuntu versions.

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

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

Title:
  mousetweaks process does not get killed when entering desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem occurs on the current development version of zesty; it
  does not occur on any other Ubuntu version that is currently
  supported.

  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.

  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the
  pointer stops moving. It is an accessibility feature for example for
  people that are not able to click with an hardware device, like mouse
  buttons.

  Here is how to start the hover click in lightdm: 
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right. 
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click. 
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature. 

  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session. This was
  not the case in previous Ubuntu versions.

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

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

[Touch-packages] [Bug 1643321] Re: In the upper bar, the keyboard section can make the phone explode

[Pat McGowan]

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

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

Title:
  In the upper bar, the keyboard section can make the phone explode

Status in Canonical System Image:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  I attach a screen to explain better. In my E5 I have two keyboard
  layout; switching fast between the two cause the phone to select both
  and all the CPUs to overload making the phone unusable. The only way
  to exit is the reboot

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

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

[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

[Pat McGowan]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  indicator-datetime uses excessive memory

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

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

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

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

[Touch-packages] [Bug 1643321] Re: In the upper bar, the keyboard section can make the phone explode

[Pat McGowan]

** Also affects: indicator-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  In the upper bar, the keyboard section can make the phone explode

Status in Canonical System Image:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  I attach a screen to explain better. In my E5 I have two keyboard
  layout; switching fast between the two cause the phone to select both
  and all the CPUs to overload making the phone unusable. The only way
  to exit is the reboot

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

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

[Touch-packages] [Bug 1643673] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Till Kamppeter]

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

** This bug has been marked a duplicate of bug 1642966
   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal 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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1643673

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  i don't know, ubuntu asked me to report a bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Nov 21 11:18:22 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-07-17 (126 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat: device for Samsung-ML-191x-252x-Series: 
usb://Samsung/ML-191x%20252x%20Series?serial=Z2L8BACB300098B.
  MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC
  Papersize: letter
  PpdFiles: Samsung-ML-191x-252x-Series: Samsung ML-1915, 2.0.0
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (115 days ago)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2161
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn2161:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion TS 14 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-23T01:20:18

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

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

[Touch-packages] [Bug 1641720] Re: Selecting a day does not display all day event for that day

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-datetime -
15.10+17.04.20161116.1-0ubuntu1

---
indicator-datetime (15.10+17.04.20161116.1-0ubuntu1) zesty; urgency=medium

  * UpcomingPlanner: don't get events from the day before of the
selected one (LP: #1641720, #1641726)

 -- Marco Trevisan (Treviño)   Wed, 16 Nov 2016 23:52:50
+

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

Title:
  Selecting a day does not display all day event for that day

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  bq M10 rc-proposed silo #2195

  When I select a day from the calendar, I can see events for that day
  but it does not work with all-day events.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1641726] Re: Tapping a day displays all day event from previous day

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-datetime -
15.10+17.04.20161116.1-0ubuntu1

---
indicator-datetime (15.10+17.04.20161116.1-0ubuntu1) zesty; urgency=medium

  * UpcomingPlanner: don't get events from the day before of the
selected one (LP: #1641720, #1641726)

 -- Marco Trevisan (Treviño)   Wed, 16 Nov 2016 23:52:50
+

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

Title:
  Tapping a day displays all day event from previous day

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  bq M10 rc-proposed silo #2195

  When I tap on a day there are some events displayed, also from the day
  before.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

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

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

[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate

[Rob X]

Hi,

there is a much easier solution.
"/etc/network/if-up.d/ntpdate" use "/usr/sbin/ntpdate-debian" which read the 
configfile "/etc/default/ntpdate" (man ntpdate-debian). If you modify 
/etc/default/ntpdate with NTPOPTIONS="-u" then "/usr/sbin/ntpdate-debian" use 
an unpriviledge port (>1023) if ifup is running and don't block port udp/123 at 
the start of ntpd.

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions

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

[Touch-packages] [Bug 1643673] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Eyal Lior]

Public bug reported:

i don't know, ubuntu asked me to report a bug

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 
Date: Mon Nov 21 11:18:22 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-07-17 (126 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Lpstat: device for Samsung-ML-191x-252x-Series: 
usb://Samsung/ML-191x%20252x%20Series?serial=Z2L8BACB300098B.
MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC
Papersize: letter
PpdFiles: Samsung-ML-191x-252x-Series: Samsung ML-1915, 2.0.0
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-07-29 (115 days ago)
dmi.bios.date: 09/26/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.23
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2161
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 29.24
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn2161:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion TS 14 Notebook PC
dmi.product.version: 088110305E0620100
dmi.sys.vendor: Hewlett-Packard
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2014-07-23T01:20:18

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


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

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  i don't know, ubuntu asked me to report a bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Nov 21 11:18:22 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-07-17 (126 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat: device for Samsung-ML-191x-252x-Series: 
usb://Samsung/ML-191x%20252x%20Series?serial=Z2L8BACB300098B.
  MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC
  Papersize: letter
  PpdFiles: Samsung-ML-191x-252x-Series: Samsung ML-1915, 2.0.0
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (115 days ago)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2161
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn2161:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion TS 14 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
 

[Touch-packages] [Bug 1288786] Re: pkexec does not launch graphical authentication

[Tom Seewald]

What can be done to assist in troubleshooting this issue?

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

Title:
  pkexec does not launch graphical authentication

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Installed Trusty Tahr Lubuntu Beta1 version and added xubuntu desktop.  In 
buth desktops, I tried to launch synaptic to install some packages.  If I try 
to launch from menu, nothing seems to happen.  From a terminal, I ran
pkexec "/usr/sbin/synaptic"
   and saw that it asks for password in the terminal window, instead of popping 
up an authentication window like previous Ubuntu version did.  That was why I 
saw no authentication request when launching from menu..  I have a 
workaround)launching from Terminal window), but this should be fixed before 
release.

  ralph@minnie:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)"
  ralph@minnie:~$ pkexec --version
  pkexec version 0.105

  Thanks

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

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

[Touch-packages] [Bug 1618007] Re: Invalid property assignment in ActivityIndicatorStyle.qml

[Pat McGowan]

did not make 14, fixed in prpposed

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

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

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

Title:
  Invalid property assignment in ActivityIndicatorStyle.qml

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

Bug description:
  I get

  file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

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

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

[Julian Andres Klode]

Thanks for verifying. I should have the final update ready within the
next 16-48 hours.

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease 
 
At least one invalid signature was encountered.
  Err:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease 

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

[Seth Arnold]

Julian, I modified the script.sh to include the following line:

sudo LD_LIBRARY_PATH=$PWD/build/bin/ ./build/bin/apt-get update -o
Dir::Bin::Apt-Key="$PWD/build/bin/apt-key" -o
Dir::Bin::Methods="$PWD/build/bin/methods/" 2>&1 | tee update.log

When run from remotes/julian/for-1.2/apt-key I get the usual progress I expect.
When run from remotes/origin/1.2.y I get the errors as described above.

Oddly enough I don't see the text "The key(s) in the keyring $1 are
ignored as the file is not readable by user '$USER' executing apt-key."
in the output. (But I don't think I'm currently configured to download
sources from ddebs.ubuntu.com, which is the host corresponding to the
unreadable key.)

Thanks

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu 

[Touch-packages] [Bug 1643474] Re: sysrq k(kill) always kill the Xorg under Desktop

[dann frazier]

** Package changed: procps (Ubuntu) => linux (Ubuntu)

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

Title:
  sysrq k(kill) always kill the Xorg under Desktop

Status in linux package in Ubuntu:
  New

Bug description:
  sysrq k(kill) always kill the Xorg under Desktop.

  the best way will kill One program, chrome or vbox or java will better
  than kill Xorg.

  add one more sort key will better

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

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

[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

[Scott Moser]

I can also confirm trusty and precise as shown above.
They behave differently, in that instead of exiting failure, dhclient actually 
tries again and ends up getting an address. So in precise you would see: 


| # dhclient -6 -1 -v $dev
| Internet Systems Consortium DHCP Client 4.1-ESV-R4
| Copyright 2004-2011 Internet Systems Consortium.
| All rights reserved.
| For info, please visit https://www.isc.org/software/dhcp/
| 
| Bound to *:546
| Listening on Socket/eth0
| Sending on   Socket/eth0
| PRC: Confirming active lease (INIT-REBOOT).
| 
| XMT: Forming Confirm, 0 ms elapsed.
| XMT:  X-- IA_NA 3e:28:e6:37
| XMT:  | X-- Confirm Address fd42:198e:d2a5:1d10:1e4c:ac80:7f2e:f59e
| XMT:  V IA_NA appended.
| XMT: Confirm on eth0, interval 920ms.
| send_packet6: Cannot assign requested address
| dhc6: sendpacket6() sent -1 of 84 bytes
| [* short pause here *]
| XMT: Forming Confirm, 920 ms elapsed.
| XMT:  X-- IA_NA 3e:28:e6:37
| XMT:  | X-- Confirm Address fd42:198e:d2a5:1d10:1e4c:ac80:7f2e:f59e
| XMT:  V IA_NA appended.
| XMT: Confirm on eth0, interval 1910ms.
| send_packet6: Cannot assign requested address
| dhc6: sendpacket6() sent -1 of 84 bytes
| [* short pause here *]
| XMT: Forming Confirm, 2830 ms elapsed.
| XMT:  X-- IA_NA 3e:28:e6:37
| XMT:  | X-- Confirm Address fd42:198e:d2a5:1d10:1e4c:ac80:7f2e:f59e
| XMT:  V IA_NA appended.
| XMT: Confirm on eth0, interval 3710ms.
| RCV: Reply message on eth0 from fe80::3896:5cff:fe61:baf0.
| RCV:  X-- Server ID: 00:01:00:01:1f:c5:e1:fb:b8:ae:ed:75:5f:9a
| message status code Success: "all addresses still on link"
| PRC: Bound to lease 00:01:00:01:1f:c5:e1:fb:b8:ae:ed:75:5f:9a.


After the fix you see:
| # dhclient -6 -1 -v $dev
| Internet Systems Consortium DHCP Client 4.1-ESV-R4
| Copyright 2004-2011 Internet Systems Consortium.
| All rights reserved.
| For info, please visit https://www.isc.org/software/dhcp/
| 
| Bound to *:546
| Listening on Socket/eth0
| Sending on   Socket/eth0
| PRC: Confirming active lease (INIT-REBOOT).
| 
| XMT: Forming Confirm, 0 ms elapsed.
| XMT:  X-- IA_NA 3e:28:e6:37
| XMT:  | X-- Confirm Address fd42:198e:d2a5:1d10:1e4c:ac80:7f2e:f59e
| XMT:  V IA_NA appended.
| XMT: Confirm on eth0, interval 920ms.
| send_packet6: Cannot assign requested address
| dhc6: sendpacket6() sent -1 of 84 bytes

So I'm marking this fixed on precise and trusty also as we fix the error 
messages like:
  send_packet6: Cannot assign requested address
  dhc6: sendpacket6() sent -1 of 84 bytes



** Tags added: verification-done-precise verification-done-trusty

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Precise:
  Fix Committed
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Committed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

   Can't bind to dhcp address: Cannot assign requested address
   Please make sure there is no other dhcp server
   running and that there's no entry for dhcp or
   bootp in /etc/inetd.conf.   Also make sure you
   are not running HP JetAdmin software, which
   includes a bootp server.

   If you think you have received this message due to a bug rather
   than a configuration issue please read the section on submitting
   bugs on either our web page at www.isc.org or in the README file
   before submitting a bug.  These pages explain the proper
   process and the information we find helpful for debugging..
   $ echo $?
   1

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go 

[Touch-packages] [Bug 1643084] Re: [REGRESSION] kill segfaults w/ single, negative PID

[dann frazier]

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

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

Title:
  [REGRESSION] kill segfaults w/ single, negative PID

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  The kill binary will segfault when called w/ a single, negative PID. This 
breaks a use case where you maybe sending the default signal (SIGTERM) to all 
processes (-1) or all processes in a process group (-

[Touch-packages] [Bug 1638689] Re: package libnss3 2:3.23-0ubuntu0.14.04.1 [modified: usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/l

[Nish Aravamudan]

Hello,

Do you have any local modifications to the file
/usr/share/doc/libnss3/changelog.Debian.gz ?

Thanks,
Nish

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

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

Title:
  package libnss3 2:3.23-0ubuntu0.14.04.1 [modified:
  usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libnss3/changelog.Debian.gz', which is different from
  other instances of package libnss3:i386

Status in nss package in Ubuntu:
  Incomplete

Bug description:
  sudo aptitude upgrade
  ...
  Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.15) over (1.0.1ubuntu2.14) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libnss3_2%3a3.23-0ubuntu0.14.04.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up libapt-pkg4.12:amd64 (1.0.1ubuntu2.15) ...
  Setting up libnspr4:i386 (2:4.12-0ubuntu0.14.04.1) ...
  dpkg: dependency problems prevent configuration of libnss3-1d:i386:
   libnss3-1d:i386 depends on libnss3 (= 2:3.23-0ubuntu0.14.04.1); however:
Version of libnss3:i386 on system is 2:3.16.3-1ubuntu1.

  dpkg: error processing package libnss3-1d:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: error processing package libnss3:amd64 (--configure):
   package libnss3:amd64 2:3.23-0ubuntu0.14.04.1 cannot be configured because 
libnss3:i386 is at a different version (2:3.16.3-1ubuntu1)
  dpkg: error processing package libnss3:i386 (--configure):
   package libnss3:i386 2:3.16.3-1ubuntu1 cannot be configured because 
libnss3:amd64 is at a different version (2:3.23-0ubuntu0.14.04.1)
  dpkg: dependency problems prevent configuration of libnss3-nssdb:
   libnss3-nssdb depends on libnss3 (= 2:3.23-0ubuntu0.14.04.1); however:
Package libnss3:amd64 is not configured yet.

  dpkg: error processing package libnss3-nssdb (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
  Errors were encountered while processing:
   libnss3-1d:i386
   libnss3:amd64
   libnss3:i386
   libnss3-nssdb

  
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libnss3 2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-68-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Wed Nov  2 12:32:54 2016
  DuplicateSignature: package:libnss3:2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libnss3/changelog.Debian.gz', which is different from other 
instances of package libnss3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libnss3/changelog.Debian.gz', which is different from other 
instances of package libnss3:i386
  InstallationDate: Installed on 2015-09-22 (407 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: nss
  Title: package libnss3 2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libnss3/changelog.Debian.gz', which is 
different from other instances of package libnss3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

[Scott Moser]

I've verified that this fixes issue on yakkety.

## Set up a network in lxc that listens to dhcp ipv4 and ipv6

$ netname="v4and6"
$ profname="$netname-profile"
$ cnamepre="v4v6-"
$ lxc network create $netname
Network v4and6 created

$ lxc network set $netname ipv6.dhcp.stateful true
$ lxc profile create $profname
$ lxc profile device add $profname eth0 nic nictype=bridged parent=$netnam
Device eth0 added to v4and6-profile

$ lxc network show $netname
name: v4and6
config:
  ipv4.address: 10.152.128.1/24
  ipv4.nat: "true"
  ipv6.address: fd42:198e:d2a5:1d10::1/64
  ipv6.dhcp.stateful: "true"
  ipv6.nat: "true"
managed: true
type: bridge
usedby: []

$ lxc profile show $profname
name: v4and6-profile
config: {}
description: ""
devices:
  eth0:
nictype: bridged
parent: v4and6
type: nic
usedby: []


## Now launch a container to verify
$ rel=yakkety
$ cname=v5v6-$rel
$ lxc launch ubuntu-daily:$rel --profile=$profname $cname
$ sleep 20; # give it time to come up
% lxc exec $cname /bin/bash

## inside
$ dev=eth0;
$ ifdown $dev; ip link set down dev $dev; killall dhclient;
Killed old client process
$ dhclient -6 -1 -v $dev
...
Can't bind to dhcp address: Cannot assign requested address
Please make sure there is no other dhcp server
...
$ echo $?
1

## That verified busted. now fix.
$ ifup eth0  # brings up ipv4 dhcp properly
$ m=http://archive.ubuntu.com/ubuntu
$ echo "deb $m $(lsb_release -sc)-proposed main" | sudo tee 
/etc/apt/sources.list.d/proposed.list

$ sudo apt-get install isc-dhcp-client
$ dpkg-query --show isc-dhcp-client
isc-dhcp-client   4.3.3-5ubuntu15.1

$ ifdown $dev; ip link set down dev $dev; killall dhclient;
$ dhclient -6 -1 -v $dev 
...
message status code Success: "success"
PRC: Bound to lease 00:01:00:01:1f:c5:e1:fb:b8:ae:ed:75:5f:9a.

$ echo $?
0


** Tags added: verification-done-yakkety

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Precise:
  Fix Committed
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Committed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

   Can't bind to dhcp address: Cannot assign requested address
   Please make sure there is no other dhcp server
   running and that there's no entry for dhcp or
   bootp in /etc/inetd.conf.   Also make sure you
   are not running HP JetAdmin software, which
   includes a bootp server.

   If you think you have received this message due to a bug rather
   than a configuration issue please read the section on submitting
   bugs on either our web page at www.isc.org or in the README file
   before submitting a bug.  These pages explain the proper
   process and the information we find helpful for debugging..
   $ echo $?
   1

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1633824] Re: nautilus ignores trash on external drives

[Sadi Yumuşak]

Sorry, just noticed that this was actually fixed upstream at the end of
September, and it seems now we all should pray for Ubuntu package
maintainers to update the glib2.0 package from 2.50.0... to 2.50.1...

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

Title:
  nautilus ignores trash on external drives

Status in GLib:
  Fix Released
Status in Nautilus:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to
  trash in general. However only the items removed from permanently
  installed drives shows up in the trash virtual folder. In the case of
  usb removable drives, the .Trash-1000 folder is correctly created, and
  the files are in there but the nautilus GUI does not show those files
  in its virtual trash folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 11:48:03 2016
  InstallationDate: Installed on 2016-02-19 (239 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

[Seth Arnold]

Julian, looks like you win this year's remote-debugging-via-crystal-ball
award!

$ find /etc/apt -ls | grep sarnold
  2572875  4 -rw---   1 sarnold  sarnold  1740 Mar 23  2016 
/etc/apt/trusted.gpg.d/ddebs.gpg


Well done :D

Thanks

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed 

[Touch-packages] [Bug 1633824] Re: nautilus ignores trash on external drives

[Sadi Yumuşak]

I have this problem with removable media (USB memory stick and USB HDD,
FAT32 and NTFS) and also with my secondary internal HDD (EXT4).

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

Title:
  nautilus ignores trash on external drives

Status in GLib:
  Fix Released
Status in Nautilus:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to
  trash in general. However only the items removed from permanently
  installed drives shows up in the trash virtual folder. In the case of
  usb removable drives, the .Trash-1000 folder is correctly created, and
  the files are in there but the nautilus GUI does not show those files
  in its virtual trash folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 11:48:03 2016
  InstallationDate: Installed on 2016-02-19 (239 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Touch-packages] [Bug 1643222] Re: Merge gdk-pixbuf 2.36.0-1 (main) with Debian unstable (main)

[Michael Terry]

Hrmm...  Test failed on arm64 in the same test we patch to avoid OOM.  A
rebuild fixed it, but cause for concern.  Nothing wrong with your work.
Just looks like maybe we didn't fix that bug after all.

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

Title:
  Merge gdk-pixbuf 2.36.0-1 (main) with Debian unstable (main)

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Please merge gdk-pixbuf 2.36.0-1 (main) with Debian unstable (main)

  This update is needed by gtkm3.0 3.22:
  https://launchpad.net/ubuntu/+source/gtkmm3.0/3.22.0-1/+build/8318

  Explanation of the Ubuntu delta and why it can be dropped:
* SECURITY UPDATE: Fixes for write out-of-bounds error
 - debian/patches/CVE-2016-6352.patch: Be more careful when parsing ico
   headers. Based on upstream patch.
 - CVE-2016-6352

  The patch was backported from 2.35.3 so it's not needed any more

  This change is still needed by the Launchpad builders:
* Merge from Debian unstable (LP: #1573839).  Remaining changes:
  - Unset MALLOC_PERTURB_ for the /pixbuf/cve-2015-4491/original test, as
it fails with OOM, or gets OOM killed.

  Changelog entries since current zesty version 2.34.0-1ubuntu2:

  gdk-pixbuf (2.36.0-1) unstable; urgency=medium

* New upstream release.

   -- Michael Biebl   Mon, 19 Sep 2016 19:10:55 +0200

  gdk-pixbuf (2.35.5-1) unstable; urgency=medium

* New upstream development release.
* Drop 02-tests-Make-sure-to-NULL-terminate-the-arguments-pass.patch, merged
  upstream.
* Bump debhelper compat level to 10.
* Use dh_install --list-missing to show uninstalled files and exclude
  libtool .la files.

   -- Michael Biebl   Tue, 13 Sep 2016 16:17:03 +0200

  gdk-pixbuf (2.35.4-4) unstable; urgency=medium

* Move gtk-doc-tools and libglib2.0-doc from Build-Depends-Indep to
  Build-Depends.

   -- Michael Biebl   Thu, 08 Sep 2016 19:17:54 +0200

  gdk-pixbuf (2.35.4-3) unstable; urgency=medium

* Make sure to NULL terminate the arguments passed to g_test_get_filename().
  Otherwise the /pixbuf/composite2 test will segfault. (Closes: #837030)
* Make test-suite failures fatal again.

   -- Michael Biebl   Thu, 08 Sep 2016 18:59:21 +0200

  gdk-pixbuf (2.35.4-2) unstable; urgency=medium

* Make test-suite failures non-fatal for now to not block ongoing
  transitions.
* Build gtk-doc documentation via --enable-gtk-doc.
* Bump Standards-Version to 3.9.8.

   -- Michael Biebl   Thu, 08 Sep 2016 16:49:06 +0200

  gdk-pixbuf (2.35.4-1) unstable; urgency=medium

* New upstream release.
* Update symbols file with new additions. A few private symbols were
  dropped.
* Use dh-exec for substituting multiarch paths in libgdk-pixbuf2.0-0.install
  and libgdk-pixbuf2.0-dev.links.
* Convert from cdbs to dh.

   -- Michael Biebl   Wed, 07 Sep 2016 18:00:22 +0200

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

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

[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3

[Tyler Hicks]

Since this SRU is targeted against many source packages, I should
clarify that the last comment was specifically about gst-plugins-bad1.0
in xenial-security.

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Incomplete
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1633824] Re: nautilus ignores trash on external drives

[Launchpad Bug Tracker]

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

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nautilus ignores trash on external drives

Status in GLib:
  Fix Released
Status in Nautilus:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to
  trash in general. However only the items removed from permanently
  installed drives shows up in the trash virtual folder. In the case of
  usb removable drives, the .Trash-1000 folder is correctly created, and
  the files are in there but the nautilus GUI does not show those files
  in its virtual trash folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 11:48:03 2016
  InstallationDate: Installed on 2016-02-19 (239 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Touch-packages] [Bug 1643084] Re: [REGRESSION] kill segfaults w/ single, negative PID

[Brian Murray]

Hello dann, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
  [REGRESSION] kill segfaults w/ single, negative PID

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  The kill binary will segfault when called w/ a single, negative PID. This 
breaks a use case where you maybe sending the default signal (SIGTERM) to all 
processes (-1) or all processes in a process group (-

[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

[Scott Moser]

Martin, I'm not sure.
I just realized that the original report shows a dhclient line of 

/sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper
-pf /run/sendsigs.omit.d/network-manager.dhclient6-eth0.pid -lf
/var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf
eth0

the '-sf' is scriptfile, which defaults to dhclient-script, which is
where the patch in bug 1633479  was made. The fix proposed here was to
ifupdown, but it would seem to me that since network manager provides
its own script-file, that NetworkManager is still not fixed, unless it
somehow uses /sbin/dhclient-script (it might)

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot. It will fail to get a dhcp address during
  boot.

  [Regression Potential]

  None

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

  Related Bugs:
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)

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

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

[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3

[Tyler Hicks]

This SRU needs to be updated to incorporate the security update changes
made in 1.8.2-1ubuntu0.2 for CVE-2016-9445. Marking this bug as
verification-failed.

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-9445

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

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Incomplete
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1643222] Re: Merge gdk-pixbuf 2.36.0-1 (main) with Debian unstable (main)

[Michael Terry]

Hey Jeremy, thanks for the patch!  I've uploaded it, with one change:
you should keep old changelog entries if possible.  Helps with answering
the question "WHY are we keeping this delta" sometimes.  So I put them
back in.

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

Title:
  Merge gdk-pixbuf 2.36.0-1 (main) with Debian unstable (main)

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Please merge gdk-pixbuf 2.36.0-1 (main) with Debian unstable (main)

  This update is needed by gtkm3.0 3.22:
  https://launchpad.net/ubuntu/+source/gtkmm3.0/3.22.0-1/+build/8318

  Explanation of the Ubuntu delta and why it can be dropped:
* SECURITY UPDATE: Fixes for write out-of-bounds error
 - debian/patches/CVE-2016-6352.patch: Be more careful when parsing ico
   headers. Based on upstream patch.
 - CVE-2016-6352

  The patch was backported from 2.35.3 so it's not needed any more

  This change is still needed by the Launchpad builders:
* Merge from Debian unstable (LP: #1573839).  Remaining changes:
  - Unset MALLOC_PERTURB_ for the /pixbuf/cve-2015-4491/original test, as
it fails with OOM, or gets OOM killed.

  Changelog entries since current zesty version 2.34.0-1ubuntu2:

  gdk-pixbuf (2.36.0-1) unstable; urgency=medium

* New upstream release.

   -- Michael Biebl   Mon, 19 Sep 2016 19:10:55 +0200

  gdk-pixbuf (2.35.5-1) unstable; urgency=medium

* New upstream development release.
* Drop 02-tests-Make-sure-to-NULL-terminate-the-arguments-pass.patch, merged
  upstream.
* Bump debhelper compat level to 10.
* Use dh_install --list-missing to show uninstalled files and exclude
  libtool .la files.

   -- Michael Biebl   Tue, 13 Sep 2016 16:17:03 +0200

  gdk-pixbuf (2.35.4-4) unstable; urgency=medium

* Move gtk-doc-tools and libglib2.0-doc from Build-Depends-Indep to
  Build-Depends.

   -- Michael Biebl   Thu, 08 Sep 2016 19:17:54 +0200

  gdk-pixbuf (2.35.4-3) unstable; urgency=medium

* Make sure to NULL terminate the arguments passed to g_test_get_filename().
  Otherwise the /pixbuf/composite2 test will segfault. (Closes: #837030)
* Make test-suite failures fatal again.

   -- Michael Biebl   Thu, 08 Sep 2016 18:59:21 +0200

  gdk-pixbuf (2.35.4-2) unstable; urgency=medium

* Make test-suite failures non-fatal for now to not block ongoing
  transitions.
* Build gtk-doc documentation via --enable-gtk-doc.
* Bump Standards-Version to 3.9.8.

   -- Michael Biebl   Thu, 08 Sep 2016 16:49:06 +0200

  gdk-pixbuf (2.35.4-1) unstable; urgency=medium

* New upstream release.
* Update symbols file with new additions. A few private symbols were
  dropped.
* Use dh-exec for substituting multiarch paths in libgdk-pixbuf2.0-0.install
  and libgdk-pixbuf2.0-dev.links.
* Convert from cdbs to dh.

   -- Michael Biebl   Wed, 07 Sep 2016 18:00:22 +0200

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

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

[Touch-packages] [Bug 1504127] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From lc...@us.ibm.com 2016-11-21 12:14 EDT---
I accepted will-not-fix for this minor issue. Thanks for your comments.

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

Title:
  lsb_release throws exception if stdout is closed

Status in lsb package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Liang Chang Guo  - 2015-10-06 20:43:30 ==
  For testing if a system is Ubuntu, the following combined command with bash 
always gets extra BrokenPipeError on Ubuntu (14.04 to 15.10):

  # ( cat /etc/os-release /proc/version; lsb_release -is ) | grep -iq Ubuntu 
  Exception ignored in: <_io.TextIOWrapper name='' mode='w' 
encoding='UTF-8'>
  BrokenPipeError: [Errno 32] Broken pipe

  While the return code is correct:
  # ( cat /etc/os-release /proc/version; lsb_release -is ) | grep -iq Ubuntu && 
echo It-is-Ubuntu
  Exception ignored in: <_io.TextIOWrapper name='' mode='w' 
encoding='UTF-8'>
  BrokenPipeError: [Errno 32] Broken pipe
  It-is-Ubuntu

  It may work well if with slight changes for the command:
  # ( cat /etc/os-release /proc/version; lsb_release -is ) | grep -i Ubuntu
  NAME="Ubuntu"
  ... ...
  # ( cat /etc/os-release /proc/version; lsb_release -is ) | grep -iq UbuntuW
  # ( cat /etc/os-release /proc/version; sleep 1; echo =; lsb_release -is ) | 
grep -iq Ubuntu
  # cat /etc/os-release /proc/version | grep -iq Ubuntu
  # (lsb_release -is) | grep -iq Ubuntu

  *** Ubuntu Platform Info ***
  # uname -a
  Linux ubt1510J2 4.2.0-12-generic #14-Ubuntu SMP Mon Sep 28 16:50:34 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux

  # dpkg -l bash grep
  ||/ Name  Version   Architecture  
Description
  
+++-=-=-=-=
  ii  bash  4.3-14ubuntu1 ppc64el   
GNU Bourne Again SHell
  ii  grep  2.21-2ppc64el   
GNU grep, egrep and fgrep

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

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

[Touch-packages] [Bug 1637574] Re: popt feature request: poptStringFromArgv

[Nish Aravamudan]

Thank you for filing this bug report! Given that the last Debian release
was in 2014 and the last upstream release was in 2010, I'm not sure it's
fair to ask you to submit this report to either upstream or Debian
(although I did find https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=656105 for Debian, submitted by you, so thank you
for that!).

Unfortunately, this seems more appropriate as an upstream issue. It will
take someone with subject matter expertise to implement new
functionality.

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

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

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

Title:
  popt feature request: poptStringFromArgv

Status in popt package in Ubuntu:
  New

Bug description:
  Feature request: the addition of a poptStringFromArgv that does the
  opposite of poptParseArgvString: that is, turn a supplied argv, argc
  pair into a canonically-equivalent string.

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

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

[Touch-packages] [Bug 1643634] Re: /bin/kill:11:__GI_____strtol_l_internal:__strtol:atoi:kill_main:main

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1643084
   [REGRESSION] kill segfaults w/ single, negative PID

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

Title:
  /bin/kill:11:__GI_strtol_l_internal:__strtol:atoi:kill_main:main

Status in procps package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
procps.  This problem was most recently seen with package version 
2:3.3.12-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/ca3851bccaed9924746cc8551188f9039c162093 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1643634] [NEW] /bin/kill:11:__GI_____strtol_l_internal:__strtol:atoi:kill_main:main

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
procps.  This problem was most recently seen with package version 
2:3.3.12-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/ca3851bccaed9924746cc8551188f9039c162093 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: xenial yakkety

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

Title:
  /bin/kill:11:__GI_strtol_l_internal:__strtol:atoi:kill_main:main

Status in procps package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
procps.  This problem was most recently seen with package version 
2:3.3.12-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/ca3851bccaed9924746cc8551188f9039c162093 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1637573] Re: popt man pages are incomplete and erroneous

[Nish Aravamudan]

Thank you for filing this bug report! Given that the last Debian release
was in 2014 and the last upstream release was in 2010, I'm not sure it's
fair to ask you to submit this report to either upstream or Debian
(although I did find https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=656105 for Debian, submitted by you, so thank you
for that!).

Unfortunately, these do seem like upstream issues. It will take someone
time to determine the answer to 1), at least. I will leave this bug
open, but I'm not sure when and if it will get resolved.

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

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

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

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

Title:
  popt man pages are incomplete and erroneous

Status in popt package in Ubuntu:
  Triaged

Bug description:
  Error in popt man pages: the e-address e...@redhat.com is invalid
  (probably has been for quite some time)

  Omissions in popt man pages:

  1) poptParseArgvString has an undocumented return int value. What does
  it return and what does it mean?

  2) poptGetArg recovers “leftover arguments” but its documentation
  fails to make it clear that it should not be called until
  poptGetNextOpt has returned -1.  I ran into this with an app that used
  popt but knew that it had no options to check for: after generating
  the context with poptGetContext, it tried to jump directly to
  poptGetArg, with disastrous results.

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

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

[Touch-packages] [Bug 1643386] Re: drive.google.com showing mobile site on desktop

[Olivier Tilloy]

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

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

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

Title:
  drive.google.com showing mobile site on desktop

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  need an override for drive.google.com on desktop as it currently shows
  mobile version which is incorrect

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

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

[Touch-packages] [Bug 1643386] Re: drive.google.com showing mobile site on desktop

[Launchpad Bug Tracker]

** Branch linked: lp:~osomon/webbrowser-app/gdrive-ua-override-1643386

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

Title:
  drive.google.com showing mobile site on desktop

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  need an override for drive.google.com on desktop as it currently shows
  mobile version which is incorrect

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

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

[Touch-packages] [Bug 1624251] Re: gsettings-qt fails test_reset() property count on Qt 5.7.1

[Albert Astals Cid]

It's a regression in Qt, i'm working on it

** Changed in: gsettings-qt (Ubuntu)
 Assignee: (unassigned) => Albert Astals Cid (aacid)

** Changed in: gsettings-qt (Ubuntu)
   Status: New => In Progress

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

Title:
  gsettings-qt fails test_reset() property count on Qt 5.7.1

Status in gsettings-qt package in Ubuntu:
  In Progress

Bug description:
  --
  FAIL!  : GSettings::test_reset() property count
 Actual   (): 0
 Expected (): 1
 Loc: 
[/«BUILDDIR»/gsettings-qt-0.1+16.04.20160329/tests/tst_GSettings.qml(102)]

  (process:7207): GLib-GIO-WARNING **: g_settings_set_value: value for key 
'test-enum' in schema 'com.canonical.gsettings.Test' is outside of valid range
  --

  (https://launchpadlibrarian.net/284597323/buildlog_ubuntu-yakkety-
  amd64.gsettings-qt_0.1+16.04.20160329-0ubuntu2~5_BUILDING.txt.gz)

  More information about Qt 5.7 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

[Scott Moser]

** Description changed:

  [Impact]
  
  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:
  
  Can't bind to dhcp address: Cannot assign requested address
  
  This is because ifupdown doesn't wait, after bringing the interface up,
  for it to complete its link-local Duplicate Address Detection (DAD), and
  the dhcp client can't bind to the link-local address because it's still
  in "tentative" state (until DAD completes).
  
  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.
  
  [Test Case]
  
  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot. It will fail to get a dhcp address during boot.
  
  [Regression Potential]
  
  None
  
  [Other Info]
  
  After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6
  address via DHCPv6. The root cause is that dhclient is exiting with the
  following message:
  
  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.
  
  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..
  
  exiting.
  -
  
  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.
  
  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:
  
  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d/network-
  manager.dhclient-eth0.pid -lf /var/lib/NetworkManager/dhclient-c0a3dfde-
  5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager
  /dhclient-eth0.conf eth0
  
  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d/network-
  manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6
  -c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0
  
  I do not see anything suspicious with the way both dhclients are
  invoked.
  
  Given that a downgrade allows me to obtain an IPv6 address I think this
  might be a bug in the ISC DHCP client rather than in NetworkManager.
+ 
+ Related Bugs:
+  * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot. It will fail to get a dhcp address during
  boot.

  [Regression Potential]

  None

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also 

[Touch-packages] [Bug 1573296] Re: obsolete conffiles not cleaned up on upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.1

---
pulseaudio (1:8.0-0ubuntu3.1) xenial; urgency=medium

  * debian/pulseaudio.maintscript: Bump versions for files that need to be
removed as they are obsolete (LP: #1573296)
  * 0502-bluetooth-bluez5-bring-back-SCO-over-PCM-support.patch:
- Remove patch hunk that set u->transport to NULL. At the time this
  code was written for 15.10, it was to prevent an assertion. Now with
  newer versions of pulse, the opposite is happening in some circumstances
  (LP: #1574324)

 -- Luke Yelavich   Thu, 03 Nov 2016 16:58:35 +1100

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

Title:
  obsolete conffiles not cleaned up on upgrade

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

Bug description:
  Impact:

  When upgrading to xenial from earlier releases, some files are left on
  the user's system. They are not used, but may otherwise be mistaken
  for being used by the user if they are attempting to fix a problem.

  Regression potential:

  Low to none, as the relevant files are not used, and are being removed
  when the updated version of Pulseaudio is installed. These files are
  already removed in yakkety and later.

  Test case:

  When updating from trusty to xenial, one will note the presence of the
  below listed files on the system. Updating from pulseaudio in xenial
  or pulseaudio in trusty to what is in xenial-proposed shoudl delete
  the listed files. The /etc/init.d/pulseaudio script should also be
  unregistered.

  
  Original bug report:

  The following files are marked obsolete after the upgrade to 16.04:

   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

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

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

[Martin Pitt]

The verification of the Stable Release Update for pulseaudio 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 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:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  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 1559731] Proposed package removed from archive

[Martin Pitt]

The version of indicator-power in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

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

Title:
  Battery indicator turns red at 30% on desktop

Status in Canonical System Image:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power source package in Xenial:
  Won't Fix

Bug description:
  The indicator turns red as soon as battery goes 30%

  Please refer to the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-power 12.10.6+16.04.20160105-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 20 20:43:32 2016
  InstallationDate: Installed on 2016-03-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313)
  SourcePackage: indicator-power
  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/1559731/+subscriptions

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

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:9.0-2ubuntu2.1

---
pulseaudio (1:9.0-2ubuntu2.1) yakkety; urgency=medium

  * 0502-bluetooth-bluez5-bring-back-SCO-over-PCM-support.patch:
- Remove patch hunk that set u->transport to NULL. At the time this
  code was written for 15.10, it was to prevent an assertion. Now with
  newer versions of pulse, the opposite is happening in some circumstances
  (LP: #1574324)

 -- Luke Yelavich   Thu, 03 Nov 2016 16:57:47 +1100

** Changed in: pulseaudio (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: pulseaudio (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 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:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  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 1559731] Proposed package removed from archive

[Martin Pitt]

The version of indicator-power in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

** Changed in: indicator-power (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

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

Title:
  Battery indicator turns red at 30% on desktop

Status in Canonical System Image:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power source package in Xenial:
  Won't Fix

Bug description:
  The indicator turns red as soon as battery goes 30%

  Please refer to the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-power 12.10.6+16.04.20160105-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 20 20:43:32 2016
  InstallationDate: Installed on 2016-03-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313)
  SourcePackage: indicator-power
  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/1559731/+subscriptions

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

[Touch-packages] [Bug 1573296] Update Released

[Martin Pitt]

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

Title:
  obsolete conffiles not cleaned up on upgrade

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

Bug description:
  Impact:

  When upgrading to xenial from earlier releases, some files are left on
  the user's system. They are not used, but may otherwise be mistaken
  for being used by the user if they are attempting to fix a problem.

  Regression potential:

  Low to none, as the relevant files are not used, and are being removed
  when the updated version of Pulseaudio is installed. These files are
  already removed in yakkety and later.

  Test case:

  When updating from trusty to xenial, one will note the presence of the
  below listed files on the system. Updating from pulseaudio in xenial
  or pulseaudio in trusty to what is in xenial-proposed shoudl delete
  the listed files. The /etc/init.d/pulseaudio script should also be
  unregistered.

  
  Original bug report:

  The following files are marked obsolete after the upgrade to 16.04:

   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.1

---
pulseaudio (1:8.0-0ubuntu3.1) xenial; urgency=medium

  * debian/pulseaudio.maintscript: Bump versions for files that need to be
removed as they are obsolete (LP: #1573296)
  * 0502-bluetooth-bluez5-bring-back-SCO-over-PCM-support.patch:
- Remove patch hunk that set u->transport to NULL. At the time this
  code was written for 15.10, it was to prevent an assertion. Now with
  newer versions of pulse, the opposite is happening in some circumstances
  (LP: #1574324)

 -- Luke Yelavich   Thu, 03 Nov 2016 16:58:35 +1100

-- 
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:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Martin Pitt]

Comment #123 provided verification in yakkety.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Martin Pitt]

** Changed in: pulseaudio (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 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:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  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 1089013] Proposed package removed from archive

[Martin Pitt]

The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.

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

Title:
  clvm startup script requires cman

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Precise:
  Triaged
Status in lvm2 source package in Trusty:
  Won't Fix
Status in lvm2 source package in Wily:
  Won't Fix
Status in lvm2 source package in Xenial:
  Fix Released

Bug description:
  while clvm in precise can support corosync, init script won't start
  because issues a cman status command

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: clvm 2.02.66-4ubuntu7.1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Tue Dec 11 18:09:36 2012
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=screen
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.clvm: [modified]
  mtime.conffile..etc.default.clvm: 2012-12-11T16:45:40.149014

  [Impact]

   * clvm daemon cannot start using provided init scripts

  [Test Case]

   * Install clvm package
   * Configure corosync
   * service clvm start
     - Fails to start due to cman dependency

  [Regression Potential]

   * None, already broken, though there is risk of other bugs being
  uncovered since this hasn't worked in quite awhile.

  [Other Info]

   * This is a change to the debian provided init script for clvm. Upstream
     debian still has the redhat-cluster package which contains the cman
     tool, as such this change is applicable to Ubuntu only since the
     redhat clustering suite is not available.

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

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

[Touch-packages] [Bug 1089013] Proposed package removed from archive

[Martin Pitt]

The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.

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

Title:
  clvm startup script requires cman

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Precise:
  Triaged
Status in lvm2 source package in Trusty:
  Won't Fix
Status in lvm2 source package in Wily:
  Won't Fix
Status in lvm2 source package in Xenial:
  Fix Released

Bug description:
  while clvm in precise can support corosync, init script won't start
  because issues a cman status command

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: clvm 2.02.66-4ubuntu7.1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Tue Dec 11 18:09:36 2012
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=screen
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.clvm: [modified]
  mtime.conffile..etc.default.clvm: 2012-12-11T16:45:40.149014

  [Impact]

   * clvm daemon cannot start using provided init scripts

  [Test Case]

   * Install clvm package
   * Configure corosync
   * service clvm start
     - Fails to start due to cman dependency

  [Regression Potential]

   * None, already broken, though there is risk of other bugs being
  uncovered since this hasn't worked in quite awhile.

  [Other Info]

   * This is a change to the debian provided init script for clvm. Upstream
     debian still has the redhat-cluster package which contains the cman
     tool, as such this change is applicable to Ubuntu only since the
     redhat clustering suite is not available.

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

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

[Touch-packages] [Bug 1089013] Proposed package removed from archive

[Martin Pitt]

The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.

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

Title:
  clvm startup script requires cman

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Precise:
  Triaged
Status in lvm2 source package in Trusty:
  Won't Fix
Status in lvm2 source package in Wily:
  Won't Fix
Status in lvm2 source package in Xenial:
  Fix Released

Bug description:
  while clvm in precise can support corosync, init script won't start
  because issues a cman status command

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: clvm 2.02.66-4ubuntu7.1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Tue Dec 11 18:09:36 2012
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=screen
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.clvm: [modified]
  mtime.conffile..etc.default.clvm: 2012-12-11T16:45:40.149014

  [Impact]

   * clvm daemon cannot start using provided init scripts

  [Test Case]

   * Install clvm package
   * Configure corosync
   * service clvm start
     - Fails to start due to cman dependency

  [Regression Potential]

   * None, already broken, though there is risk of other bugs being
  uncovered since this hasn't worked in quite awhile.

  [Other Info]

   * This is a change to the debian provided init script for clvm. Upstream
     debian still has the redhat-cluster package which contains the cman
     tool, as such this change is applicable to Ubuntu only since the
     redhat clustering suite is not available.

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

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

[Touch-packages] [Bug 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG

[Marc Deslauriers]

Thanks for the debdiffs!

While they look good, there is some discussion in the upstream bug, and
the fix hasn't been committed yet. I'll wait until the fix is committed
before releasing updates for the stable releases.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Fix Released
Status in cairo source package in Precise:
  Confirmed
Status in cairo source package in Trusty:
  Confirmed
Status in cairo source package in Xenial:
  Confirmed
Status in cairo source package in Yakkety:
  Confirmed
Status in cairo package in Debian:
  Fix Released

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on yakkety. In xenial I wasn't able to reproduce the crash. I did not
  test on trusty.

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

[Launchpad Bug Tracker]

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

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

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

Title:
  incorrect UI scale on high-resolution desktop

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

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 1089013] Proposed package removed from archive

[Martin Pitt]

The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.

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

Title:
  clvm startup script requires cman

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Precise:
  Triaged
Status in lvm2 source package in Trusty:
  Won't Fix
Status in lvm2 source package in Wily:
  Won't Fix
Status in lvm2 source package in Xenial:
  Fix Released

Bug description:
  while clvm in precise can support corosync, init script won't start
  because issues a cman status command

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: clvm 2.02.66-4ubuntu7.1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Tue Dec 11 18:09:36 2012
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=screen
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.clvm: [modified]
  mtime.conffile..etc.default.clvm: 2012-12-11T16:45:40.149014

  [Impact]

   * clvm daemon cannot start using provided init scripts

  [Test Case]

   * Install clvm package
   * Configure corosync
   * service clvm start
     - Fails to start due to cman dependency

  [Regression Potential]

   * None, already broken, though there is risk of other bugs being
  uncovered since this hasn't worked in quite awhile.

  [Other Info]

   * This is a change to the debian provided init script for clvm. Upstream
     debian still has the redhat-cluster package which contains the cman
     tool, as such this change is applicable to Ubuntu only since the
     redhat clustering suite is not available.

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

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

[Touch-packages] [Bug 1089013] Proposed package removed from archive

[Martin Pitt]

The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.

** Changed in: lvm2 (Ubuntu Trusty)
   Status: Fix Committed => Won't Fix

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

Title:
  clvm startup script requires cman

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Precise:
  Triaged
Status in lvm2 source package in Trusty:
  Won't Fix
Status in lvm2 source package in Wily:
  Won't Fix
Status in lvm2 source package in Xenial:
  Fix Released

Bug description:
  while clvm in precise can support corosync, init script won't start
  because issues a cman status command

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: clvm 2.02.66-4ubuntu7.1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Tue Dec 11 18:09:36 2012
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=screen
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.clvm: [modified]
  mtime.conffile..etc.default.clvm: 2012-12-11T16:45:40.149014

  [Impact]

   * clvm daemon cannot start using provided init scripts

  [Test Case]

   * Install clvm package
   * Configure corosync
   * service clvm start
     - Fails to start due to cman dependency

  [Regression Potential]

   * None, already broken, though there is risk of other bugs being
  uncovered since this hasn't worked in quite awhile.

  [Other Info]

   * This is a change to the debian provided init script for clvm. Upstream
     debian still has the redhat-cluster package which contains the cman
     tool, as such this change is applicable to Ubuntu only since the
     redhat clustering suite is not available.

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

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