[Touch-packages] [Bug 1635508] Re: Tracker sets number of inotify watches to a ridiculously low number

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

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

Title:
  Tracker sets number of inotify watches to a ridiculously low number

Status in tracker package in Ubuntu:
  New

Bug description:
  I have been trying to get Ubuntu to ship with a sane amount of inotify
  watches for the past few years and so far there hasn't been any
  progress made with that. I've noticed that Tracker increases the
  number of watches which is a very good thing! Unfortunately, this
  number is way too low to be useful on any modern desktop computer.

  The current limit set by tracker is set to 65536 which is somewhat an
  improvement over the useless 8192 default but to be useful, and not
  show false error messages about full disk drives, inotify needs at
  least 524288 watches or better 1048576 (which is the value used by the
  InSync client).

  The sad thing is, when kde-runtime is installed the 30-baloo-inotify-
  limit.conf file sets the value to 524288 but unfortunately, 't' comes
  after 'b' in the alphabet hence tracker overrides that nice and sane
  value to one that will confuse pretty much any user with cryptic and
  false messages about full hard drives. (WD=-1, Errno=No space left on
  device (ENOSPC))

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: tracker-miner-fs 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 20 20:35:38 2016
  InstallationDate: Installed on 2015-05-15 (525 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (1 days ago)

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

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


[Touch-packages] [Bug 1644653] Re: tracker broken for KDE/X/lightdm

2016-12-09 Thread Jeremy Bicha
(and log out completely and log back in afterwards or reboot)

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

Title:
  tracker broken for KDE/X/lightdm

Status in tracker package in Ubuntu:
  New

Bug description:
  tracker 1.6.2-0ubuntu1.1 on 16.04 could be made to work for KDE/X/lightdm
  - https://bugzilla.gnome.org/show_bug.cgi?id=769715#c12
  - DBUS_SESSION_BUS_ADDRESS has an incorrect value

  on 16.10 it’s beyond repair:

  dpkg --status tracker | egrep ^V
  Version: 1.10.0-1ubuntu1

  tracker reset hard && tracker daemon --start && tracker daemon 
--list-processes
  Found process ID 23118 for 'tracker-extract'
  Found process ID 23135 for 'tracker-store'
  Found process ID 23145 for 'tracker-miner-user-guides'
  Found process ID 23150 for 'tracker-miner-fs'
  Found process ID 23155 for 'tracker-miner-apps'
  - produces unhealthy tracker

  A healthy tracker has one or two tracker entries
  tracker daemon --start && tracker daemon --list-processes
  Starting miners…
✓ Userguides
✓ File System
✓ Applications
✓ Extractor
  Found 6 PIDs…
  Found process ID 4185 for 'tracker-store'
  Found process ID 4196 for 'tracker-miner-fs'
  Found process ID 4201 for 'tracker-miner-apps'
  Found process ID 4207 for 'tracker-extract'
  Found process ID 4229 for 'tracker'
  Found process ID 4921 for 'tracker-miner-user-guides'

  16/10/Unity 8 and 16.10/GNOME/Wayland are healthy, kde is not

  On login tracker kind of works, but after a while the 'tracker' entry
  dies and tracker is no longer with us.

  There are some new fancy race conditions, too:

  on reset occasionally
  (tracker daemon:13618): Tracker-CRITICAL **: Could not create proxy on the 
D-Bus session bus, Error calling StartServiceByName for 
org.freedesktop.Tracker1.Miner.Extract: Timeout was reached

  on list processes occasionally:
  Could not stat() file '/proc/21722', Error when getting information for file 
'/proc/21722': No such file or directoryFound 5 PIDs…

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tracker 1.6.2-0ubuntu1.1
  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
  Date: Thu Nov 24 13:57:04 2016
  InstallationDate: Installed on 2016-08-26 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1644653] Re: tracker broken for KDE/X/lightdm

2016-12-09 Thread Jeremy Bicha
Just a blind guess, but does it help if you install dbus-user-session ?

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

Title:
  tracker broken for KDE/X/lightdm

Status in tracker package in Ubuntu:
  New

Bug description:
  tracker 1.6.2-0ubuntu1.1 on 16.04 could be made to work for KDE/X/lightdm
  - https://bugzilla.gnome.org/show_bug.cgi?id=769715#c12
  - DBUS_SESSION_BUS_ADDRESS has an incorrect value

  on 16.10 it’s beyond repair:

  dpkg --status tracker | egrep ^V
  Version: 1.10.0-1ubuntu1

  tracker reset hard && tracker daemon --start && tracker daemon 
--list-processes
  Found process ID 23118 for 'tracker-extract'
  Found process ID 23135 for 'tracker-store'
  Found process ID 23145 for 'tracker-miner-user-guides'
  Found process ID 23150 for 'tracker-miner-fs'
  Found process ID 23155 for 'tracker-miner-apps'
  - produces unhealthy tracker

  A healthy tracker has one or two tracker entries
  tracker daemon --start && tracker daemon --list-processes
  Starting miners…
✓ Userguides
✓ File System
✓ Applications
✓ Extractor
  Found 6 PIDs…
  Found process ID 4185 for 'tracker-store'
  Found process ID 4196 for 'tracker-miner-fs'
  Found process ID 4201 for 'tracker-miner-apps'
  Found process ID 4207 for 'tracker-extract'
  Found process ID 4229 for 'tracker'
  Found process ID 4921 for 'tracker-miner-user-guides'

  16/10/Unity 8 and 16.10/GNOME/Wayland are healthy, kde is not

  On login tracker kind of works, but after a while the 'tracker' entry
  dies and tracker is no longer with us.

  There are some new fancy race conditions, too:

  on reset occasionally
  (tracker daemon:13618): Tracker-CRITICAL **: Could not create proxy on the 
D-Bus session bus, Error calling StartServiceByName for 
org.freedesktop.Tracker1.Miner.Extract: Timeout was reached

  on list processes occasionally:
  Could not stat() file '/proc/21722', Error when getting information for file 
'/proc/21722': No such file or directoryFound 5 PIDs…

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tracker 1.6.2-0ubuntu1.1
  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
  Date: Thu Nov 24 13:57:04 2016
  InstallationDate: Installed on 2016-08-26 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1648921] Re: Sandbox the tracker extractor

2016-12-09 Thread Jeremy Bicha
I went ahead and uploaded this for yakkety as a regular SRU (it's in the
unapproved queue now)

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Xenial:
  New
Status in tracker source package in Yakkety:
  In Progress

Bug description:
  * SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
  - extractor's filesystem and network access is limited to being read and
    local only (LP: #1648921)
  - No CVE number

  The tracker developers have recently confined their extractor to
  attempt to make tracker more resilient to attacks, especially
  involving flaws in gstreamer parsers.

  There is no CVE number assigned to this issue.

  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html

  The gstreamer security fixes are being handled separately. See bug
  1619600

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

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


[Touch-packages] [Bug 1648921] Re: Sandbox the tracker extractor

2016-12-09 Thread Jeremy Bicha
** Tags added: xenial yakkety zesty

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

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

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Xenial:
  New
Status in tracker source package in Yakkety:
  In Progress

Bug description:
  * SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
  - extractor's filesystem and network access is limited to being read and
    local only (LP: #1648921)
  - No CVE number

  The tracker developers have recently confined their extractor to
  attempt to make tracker more resilient to attacks, especially
  involving flaws in gstreamer parsers.

  There is no CVE number assigned to this issue.

  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html

  The gstreamer security fixes are being handled separately. See bug
  1619600

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

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


[Touch-packages] [Bug 1648938] [NEW] Update tracker to 1.10.2

2016-12-09 Thread Jeremy Bicha
Public bug reported:

Impact
=
This update includes the new bugfix releases 1.10.1 and 1.10.2
https://git.gnome.org/browse/tracker/tree/NEWS?h=tracker-1.10
https://git.gnome.org/browse/tracker/log?h=tracker-1.10

The major change is that the tracker extractor is now confined by
libseccomp for better security (LP: #1648921)

Test Case
=
I recommend testing with Ubuntu GNOME 16.10 since it includes tracker.
1. After installing the update, log out and log back in just to make sure 
you're running the updated tracker
2. Download some pictures or music files to an indexed folder (~/Downloads, 
~/Music, ~/Pictures are good)
3. Wait a few moments and see if the files show up in the GNOME Music app, the 
GNOME Photos app, and/or the GNOME Shell Activities Overview when searching for 
that filename.
4. You can also look for any tracker errors to show up in the GNOME Logs app 
(gnome-logs is a frontend to the systemd journal)

Regression Potential

Low. Ensure that tracker still works.

** Affects: tracker (Ubuntu)
 Importance: Low
 Status: Fix Released

** Affects: tracker (Ubuntu Yakkety)
 Importance: Low
 Status: In Progress


** Tags: upgrade-software-version yakkety zesty

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

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

** Changed in: tracker (Ubuntu Yakkety)
   Importance: Undecided => Low

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

Title:
  Update tracker to 1.10.2

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Yakkety:
  In Progress

Bug description:
  Impact
  =
  This update includes the new bugfix releases 1.10.1 and 1.10.2
  https://git.gnome.org/browse/tracker/tree/NEWS?h=tracker-1.10
  https://git.gnome.org/browse/tracker/log?h=tracker-1.10

  The major change is that the tracker extractor is now confined by
  libseccomp for better security (LP: #1648921)

  Test Case
  =
  I recommend testing with Ubuntu GNOME 16.10 since it includes tracker.
  1. After installing the update, log out and log back in just to make sure 
you're running the updated tracker
  2. Download some pictures or music files to an indexed folder (~/Downloads, 
~/Music, ~/Pictures are good)
  3. Wait a few moments and see if the files show up in the GNOME Music app, 
the GNOME Photos app, and/or the GNOME Shell Activities Overview when searching 
for that filename.
  4. You can also look for any tracker errors to show up in the GNOME Logs app 
(gnome-logs is a frontend to the systemd journal)

  Regression Potential
  
  Low. Ensure that tracker still works.

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

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


[Touch-packages] [Bug 1612835] Re: Please don't depend on jasper

2016-12-09 Thread Jeremy Bicha
** Description changed:

  Jasper is being removed from Debian. It would be great if this could be
  done in Ubuntu too before 16.10 is released.
  
- https://release.debian.org/transitions/html/jasper-rm.html
+ 
https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html
+ /jasper-rm.html
  
  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)
  
  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

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

Title:
  Please don't depend on jasper

Status in digikam package in Ubuntu:
  New
Status in jasper package in Ubuntu:
  New
Status in kde4libs package in Ubuntu:
  New
Status in kimageformats package in Ubuntu:
  Fix Released
Status in kopete package in Ubuntu:
  New

Bug description:
  Jasper is being removed from Debian. It would be great if this could
  be done in Ubuntu too before 16.10 is released.

  
https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html
  /jasper-rm.html

  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)

  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

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

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


[Touch-packages] [Bug 1612835] Re: Please don't depend on jasper

2016-12-09 Thread Jeremy Bicha
kimageformats is done in zesty-proposed:
https://launchpad.net/ubuntu/+source/kimageformats/5.28.0-0ubuntu1

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

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

Title:
  Please don't depend on jasper

Status in digikam package in Ubuntu:
  New
Status in jasper package in Ubuntu:
  New
Status in kde4libs package in Ubuntu:
  New
Status in kimageformats package in Ubuntu:
  Fix Released
Status in kopete package in Ubuntu:
  New

Bug description:
  Jasper is being removed from Debian. It would be great if this could
  be done in Ubuntu too before 16.10 is released.

  https://release.debian.org/transitions/html/jasper-rm.html

  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)

  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

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

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


[Touch-packages] [Bug 1612835] Re: Please don't depend on jasper

2016-12-09 Thread Jeremy Bicha
** Description changed:

  Jasper is being removed from Debian. It would be great if this could be
  done in Ubuntu too before 16.10 is released.
  
  https://release.debian.org/transitions/html/jasper-rm.html
  
  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
- * dcraw (fixed in -proposed, autosynced from Debian but ftbfs, see bug 
1611001 )
- * kodi  (for libjasper-dev) (in sync with Debian, so 
we'll just sync their fix)
- 
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)
  
  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

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

Title:
  Please don't depend on jasper

Status in digikam package in Ubuntu:
  New
Status in jasper package in Ubuntu:
  New
Status in kde4libs package in Ubuntu:
  New
Status in kimageformats package in Ubuntu:
  Fix Released
Status in kopete package in Ubuntu:
  New

Bug description:
  Jasper is being removed from Debian. It would be great if this could
  be done in Ubuntu too before 16.10 is released.

  https://release.debian.org/transitions/html/jasper-rm.html

  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)

  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

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

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


[Touch-packages] [Bug 1648931] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed -

2016-12-09 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed  -

Status in gconf package in Ubuntu:
  New

Bug description:
  This was a reported error during upgrade from 16.04 to 16.10.
  Previously 14.04 and have not used any software yet so I am unaware of
  what manifestations the bug may have on the GUI or system.  Literally
  upgraded and updated from 14.04 to 16.04 to 16.10 right after
  installation.

  I don't if it's a bug.  The system sent me here and started my
  internet for this.  I am using Security Onion.

  Again, this was a message during upgrade and nothing else was open on
  my computer.  Just the message and it continued to upgrade.

  Regards,

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-31.33-generic 4.8.11
  Uname: Linux 4.8.0-31-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec  9 20:07:26 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-12-10 (0 days ago)
  InstallationMedia: SecurityOnion 14.04 - Release amd64
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-12-10 (0 days ago)

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

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


[Touch-packages] [Bug 1648931] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed -

2016-12-09 Thread Jay
Public bug reported:

This was a reported error during upgrade from 16.04 to 16.10.
Previously 14.04 and have not used any software yet so I am unaware of
what manifestations the bug may have on the GUI or system.  Literally
upgraded and updated from 14.04 to 16.04 to 16.10 right after
installation.

I don't if it's a bug.  The system sent me here and started my internet
for this.  I am using Security Onion.

Again, this was a message during upgrade and nothing else was open on my
computer.  Just the message and it continued to upgrade.

Regards,

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: gconf2 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.8.0-31.33-generic 4.8.11
Uname: Linux 4.8.0-31-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Dec  9 20:07:26 2016
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2016-12-10 (0 days ago)
InstallationMedia: SecurityOnion 14.04 - Release amd64
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to yakkety on 2016-12-10 (0 days ago)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed  -

Status in gconf package in Ubuntu:
  New

Bug description:
  This was a reported error during upgrade from 16.04 to 16.10.
  Previously 14.04 and have not used any software yet so I am unaware of
  what manifestations the bug may have on the GUI or system.  Literally
  upgraded and updated from 14.04 to 16.04 to 16.10 right after
  installation.

  I don't if it's a bug.  The system sent me here and started my
  internet for this.  I am using Security Onion.

  Again, this was a message during upgrade and nothing else was open on
  my computer.  Just the message and it continued to upgrade.

  Regards,

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-31.33-generic 4.8.11
  Uname: Linux 4.8.0-31-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec  9 20:07:26 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-12-10 (0 days ago)
  InstallationMedia: SecurityOnion 14.04 - Release amd64
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-12-10 (0 days ago)

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

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


[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

2016-12-09 Thread Andrew
An update from me. I still experienced no DNS resolve a couple of times
on first boot up with the patched version. I am using Xenial 16.04 by
the way.

~$ uname -r
4.4.0-53-generic

~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  
  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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


[Touch-packages] [Bug 1630969] Re: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

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

** Changed in: android-tools (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 5

Status in android-tools package in Ubuntu:
  Expired

Bug description:
  that package is not upgadable, that is all i can say, sorry)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Oct  6 04:03:47 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 5
  InstallationDate: Installed on 2016-09-23 (13 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160726)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: android-tools
  Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

2016-12-09 Thread Eric Desrochers
I worked on a patch that so far seems to work well.

I still need to arrange a few things, but I should be able to submit a
patch soon.

The patch will create a additional binary package.

isc-dhcp-client pkg  : dhclient with DDNS functionality disabled (no random 
extra ports)
isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

Eric


** Changed in: isc-dhcp (Ubuntu Trusty)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: isc-dhcp (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: Confirmed => In Progress

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

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

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


[Touch-packages] [Bug 1648921] Re: Sandbox the tracker extractor

2016-12-09 Thread Jeremy Bicha
tracker was not included by default in any Ubuntu 12.04 flavor and
libseccomp is only available in backports there.

I don't intend to try to backport this change for Ubuntu 14.04 either.
Ubuntu GNOME 14.04 has only a few months of support left. I don't feel
it's worth the work to try to make these changes there.

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  New
Status in tracker source package in Xenial:
  New
Status in tracker source package in Yakkety:
  New

Bug description:
  * SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
  - extractor's filesystem and network access is limited to being read and
    local only (LP: #1648921)
  - No CVE number

  The tracker developers have recently confined their extractor to
  attempt to make tracker more resilient to attacks, especially
  involving flaws in gstreamer parsers.

  There is no CVE number assigned to this issue.

  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html

  The gstreamer security fixes are being handled separately. See bug
  1619600

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

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


[Touch-packages] [Bug 1648921] Re: Sandbox the tracker extractor

2016-12-09 Thread Jeremy Bicha
** Description changed:

-   * SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
- - extractor's filesystem and network access is limited to being read and
-   local only (LP: #1619600)
- - No CVE number
+ * SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
+ - extractor's filesystem and network access is limited to being read and
+   local only (LP: #1648921)
+ - No CVE number
  
  The tracker developers have recently confined their extractor to attempt
  to make tracker more resilient to attacks, especially involving flaws in
  gstreamer parsers.
  
  There is no CVE number assigned to this issue.
  
  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html
  
  The gstreamer security fixes are being handled separately. See bug
  1619600

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

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

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  New
Status in tracker source package in Xenial:
  New
Status in tracker source package in Yakkety:
  New

Bug description:
  * SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
  - extractor's filesystem and network access is limited to being read and
    local only (LP: #1648921)
  - No CVE number

  The tracker developers have recently confined their extractor to
  attempt to make tracker more resilient to attacks, especially
  involving flaws in gstreamer parsers.

  There is no CVE number assigned to this issue.

  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html

  The gstreamer security fixes are being handled separately. See bug
  1619600

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

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


[Touch-packages] [Bug 1648925] [NEW] Accessibility menu not shown on lockscreen

2016-12-09 Thread DH
Public bug reported:

First off, I do not know for sure if this bug should be filed against
"unity-greeter" package, so some guidance from someone more in the know
would be appreciated.

When I choose to lock my session, there is no "accessibility menu" (icon
of person-figure in a circle) in the upper panel, like there is on the
login screen that shows on a fresh boot. This means that I cannot
manually turn on the onboard on-screen keyboard using only the
touchscreen. This in turn means that I cannot log in without re-docking
to my 2-in-1's keyboard.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Dec  9 19:39:17 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:191e] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:3812]
InstallationDate: Installed on 2016-11-24 (16 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 80QL
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=7b55f366-118f-45eb-aba9-a81106cfb6a7 ro quiet splash 
usbcore.autosuspend=-1 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: DFCN51WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Chelsea
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad MIIX 700-12ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrDFCN51WW:bd08/15/2016:svnLENOVO:pn80QL:pvrLenovoideapadMIIX700-12ISK:rvnLENOVO:rnChelsea:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoideapadMIIX700-12ISK:
dmi.product.name: 80QL
dmi.product.version: Lenovo ideapad MIIX 700-12ISK
dmi.sys.vendor: LENOVO
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: Fri Dec  9 19:34:07 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16708 
 vendor SDC
xserver.version: 2:1.18.4-0ubuntu0.2

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New


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

** Also affects: unity-greeter (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: xorg (Ubuntu)

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

Title:
  Accessibility menu not shown on lockscreen

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  First off, I do not know for sure if this bug should be filed against
  "unity-greeter" package, so some guidance from someone more in the
  know would be appreciated.

  When I choose to lock my session, there is no "accessibility menu"
  (icon of person-figure in a circle) in the upper panel, like there is
  on the login screen that shows on a fresh boot. This means that I
  cannot manually turn on the onboard on-screen keyboard using only the
  touchscreen. This in turn means that I cannot log in without re-
  docking to my 2-in-1's keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Uname: Linux 4.8.0-30-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: 

[Touch-packages] [Bug 1648921] Re: Sandbox the tracker extractor

2016-12-09 Thread Jeremy Bicha
** Description changed:

- The tracker developers have recently confined their extractor to attempt to 
make tracker more resilient to attacks, especially involving flaws in gstreamer 
parsers.
-  
+   * SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
+ - extractor's filesystem and network access is limited to being read and
+   local only (LP: #1619600)
+ - No CVE number
+ 
+ The tracker developers have recently confined their extractor to attempt
+ to make tracker more resilient to attacks, especially involving flaws in
+ gstreamer parsers.
+ 
  There is no CVE number assigned to this issue.
  
  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html
  
  The gstreamer security fixes are being handled separately. See bug
  1619600

** Information type changed from Public to Public Security

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  New

Bug description:
* SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
  - extractor's filesystem and network access is limited to being read and
local only (LP: #1619600)
  - No CVE number

  The tracker developers have recently confined their extractor to
  attempt to make tracker more resilient to attacks, especially
  involving flaws in gstreamer parsers.

  There is no CVE number assigned to this issue.

  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html

  The gstreamer security fixes are being handled separately. See bug
  1619600

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

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


[Touch-packages] [Bug 1648921] Re: Sandbox the tracker extractor

2016-12-09 Thread Jeremy Bicha
** Description changed:

- .
+ The tracker developers have recently confined their extractor to attempt to 
make tracker more resilient to attacks, especially involving flaws in gstreamer 
parsers.
+  
+ There is no CVE number assigned to this issue.
+ 
+ https://lwn.net/Articles/708196/
+ 
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html
+ 
+ The gstreamer security fixes are being handled separately. See bug
+ 1619600

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  New

Bug description:
  The tracker developers have recently confined their extractor to attempt to 
make tracker more resilient to attacks, especially involving flaws in gstreamer 
parsers.
   
  There is no CVE number assigned to this issue.

  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html

  The gstreamer security fixes are being handled separately. See bug
  1619600

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

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


[Touch-packages] [Bug 1648921] Re: Sandbox the tracker extractor

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

** Changed in: tracker
   Importance: Unknown => High

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  New

Bug description:
  .

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

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


[Touch-packages] [Bug 1648914] Re: Add xauth for helping X forwarding scenarios

2016-12-09 Thread Kris
** Description changed:

  Mir is separate from X so it seems counter intuitive to request xauth
  added. But let me explain.
  
  Even despite that Ubuntu Touch on devices like phones and tablets lacks
- the X stack almost entirely (except mir and what seems to be modified
+ the X stack almost entirely (except xmir and what seems to be modified
  version of gtk-x11 libs), yet the X forwarding via ssh is a viable
  scenario for the same device, even so. Because the X stack from the
  remote client will provide the display and input.
  
  Now, I myself am using X forwarding with Ubuntu Touch phone (Meizu MX4)
  and I run Gtk apps using this method. The ONLY step I had to was
  creating .Xauthority file. That is the only requirement, everything else
  is ready for the scenario. The easiest way to generated .Xauthority fule
  is with xauth tool. This is also a very light (sizewise) package, so I
  think it would be of great benefit.
  
  Optionally, I would see it of further help if possibly upon setting up 
account in newly installed Ubuntu Touch with only Mir, the .Xauthority could be 
auto-generated in the user's home.
  Because Mir and X forwarding via ssh do not conflict, they are not mutually 
exclusive.
  
  1. These changes are of tiny footprint yet improve usability greatly
  2. Users who build chroot containers will also benefit, being able to copy 
.Xauthority into the chroot so that when inside they can still instantinate X 
forwarded apps

** Description changed:

  Mir is separate from X so it seems counter intuitive to request xauth
  added. But let me explain.
  
  Even despite that Ubuntu Touch on devices like phones and tablets lacks
  the X stack almost entirely (except xmir and what seems to be modified
  version of gtk-x11 libs), yet the X forwarding via ssh is a viable
  scenario for the same device, even so. Because the X stack from the
  remote client will provide the display and input.
  
  Now, I myself am using X forwarding with Ubuntu Touch phone (Meizu MX4)
- and I run Gtk apps using this method. The ONLY step I had to was
- creating .Xauthority file. That is the only requirement, everything else
- is ready for the scenario. The easiest way to generated .Xauthority fule
- is with xauth tool. This is also a very light (sizewise) package, so I
- think it would be of great benefit.
+ and I run Gtk apps using this method. The ONLY step I had to undergo
+ beforehand was creating .Xauthority file. That is the only requirement,
+ everything else is ready for the scenario. The easiest way to generated
+ .Xauthority fule is with xauth tool. This is also a very light
+ (sizewise) package, so I think it would be of great benefit.
  
  Optionally, I would see it of further help if possibly upon setting up 
account in newly installed Ubuntu Touch with only Mir, the .Xauthority could be 
auto-generated in the user's home.
  Because Mir and X forwarding via ssh do not conflict, they are not mutually 
exclusive.
  
  1. These changes are of tiny footprint yet improve usability greatly
  2. Users who build chroot containers will also benefit, being able to copy 
.Xauthority into the chroot so that when inside they can still instantinate X 
forwarded apps

** Description changed:

  Mir is separate from X so it seems counter intuitive to request xauth
  added. But let me explain.
  
  Even despite that Ubuntu Touch on devices like phones and tablets lacks
  the X stack almost entirely (except xmir and what seems to be modified
  version of gtk-x11 libs), yet the X forwarding via ssh is a viable
  scenario for the same device, even so. Because the X stack from the
  remote client will provide the display and input.
  
  Now, I myself am using X forwarding with Ubuntu Touch phone (Meizu MX4)
  and I run Gtk apps using this method. The ONLY step I had to undergo
  beforehand was creating .Xauthority file. That is the only requirement,
- everything else is ready for the scenario. The easiest way to generated
- .Xauthority fule is with xauth tool. This is also a very light
+ everything else is ready for the scenario. The easiest way to generate
+ .Xauthority file is with xauth tool. This is also a very light
  (sizewise) package, so I think it would be of great benefit.
  
  Optionally, I would see it of further help if possibly upon setting up 
account in newly installed Ubuntu Touch with only Mir, the .Xauthority could be 
auto-generated in the user's home.
  Because Mir and X forwarding via ssh do not conflict, they are not mutually 
exclusive.
  
  1. These changes are of tiny footprint yet improve usability greatly
  2. Users who build chroot containers will also benefit, being able to copy 
.Xauthority into the chroot so that when inside they can still instantinate X 
forwarded apps

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

Title:
  Add xauth for helping X 

[Touch-packages] [Bug 1648921] [NEW] Sandbox the tracker extractor

2016-12-09 Thread Jeremy Bicha
Public bug reported:

.

** Affects: tracker
 Importance: High
 Status: Fix Released

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

** Bug watch added: GNOME Bug Tracker #764786
   https://bugzilla.gnome.org/show_bug.cgi?id=764786

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

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  New

Bug description:
  .

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

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


[Touch-packages] [Bug 762349] Re: [SRU] Difficult to distinguish which tab is selected

2016-12-09 Thread Johan Boule
In Unbuntu 16.10, the easy fix in ~/.config/gtk-3.0/gtk.css does not
work anymore.

I used to simply have this in that file :

  .notebook tab:active {
background-color: @selected_bg_color;
  }

But now, gedit does not take it into account anymore (neither gnome-
terminal but afaik they unfortunately hacked something specific just to
workaround the problem locally, and indeed it's now better-looking in
that app now).

Does anyone know what's the new css class to style to get *all* gtk tabs
look fine ?

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

Title:
  [SRU] Difficult to distinguish which tab is selected

Status in Ayatana Design:
  Fix Committed
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released

Bug description:
  [Impact]
   * When a user opens multiple tabs in GNOME terminal all tabs are styled in a 
*very* visually similar manner.  This makes it very hard to distinguish between 
the current active tab and all the others and on a HiDPI screen pretty much 
impossible.

  * This fix has been ack'd by design and was targeted for X but didn't
  get reviewed and OK'd in time.  Design team have approved this
  styling.

  * This bug is fixed by extending the CSS specifically for Terminal
  (i.e. no other applications are affected) giving the active tab a
  darker background colour (using only theme defined colours) and
  reworks the borders around the tabs to remove the graduated image
  borders that only look right on a light coloured background.  Changes
  have been made for both Ambiance and Radiance.

  [Test Case]
   * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t)
   * Open five new tabs (ctrl-shift-t)
   * Click on the tab in the middle
   * Note that it is hard to see at a glance which tab is currently selected
   * Close Terminal and all open tabs.
   * Install the patched theme
   * Open Terminal and open five new tabs
   * Click on the tab in the middle and note that it takes on a light grey 
background compared to the unselected tabs which are dark grey.

  [Regression Potential]
   * The patch only addresses tabs that are placed at the top of the window. 
However this is the only option in Terminal, so should not cause any problems.
   * There is a work-around to match the "actions bar" (the bit with the 
dropdown selector and + button).  This bug is supposed to be fixed in v3.20 and 
could be removed.  This is commented in the CSS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+subscriptions

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


[Touch-packages] [Bug 1648920] [NEW] Option does not work greeter-show-remote-login

2016-12-09 Thread nequx
Public bug reported:

I set the value of this option greeter-show-remote-login=true.
When you restart the computer, i did not see an offer remote login!
My version: lightdm 1.10.3
I make every possible logs, and I hope for your speedy assistance.

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


** Tags: archive

** Attachment added: "zip archive"
   https://bugs.launchpad.net/bugs/1648920/+attachment/4789791/+files/LOGS.zip

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

Title:
  Option does not work greeter-show-remote-login

Status in lightdm package in Ubuntu:
  New

Bug description:
  I set the value of this option greeter-show-remote-login=true.
  When you restart the computer, i did not see an offer remote login!
  My version: lightdm 1.10.3
  I make every possible logs, and I hope for your speedy assistance.

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

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


[Touch-packages] [Bug 1647603] Re: Add option for semi-transparent keyboard

2016-12-09 Thread Launchpad Bug Tracker
** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/custom-opacity

** Branch linked: lp:~michael-sheldon/ubuntu-system-settings/custom-
keyboard-opacity

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

Title:
  Add option for semi-transparent keyboard

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request.
  Especially in the landscape mode, the onscreen keyboard takes up a large 
portion of the screen. Potentially it can overlap the window where the text is 
being typed into, so you cannot see what you're typing.
  This could be VERY easily solved by letting users to set transparency level 
for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 
70% opacity on Ubuntu Touch phone, in landscape windowed mode.

  UX fix
  In System settings, the on screen keyboard option will allow a user to set 
the opacity for their OSK.

  This will be a slider in the on screen keyboard option in system
  settings, with the options to set opacity from 50%-100%

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

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


[Touch-packages] [Bug 1603416] Re: Unable to add time & date stamps to photos

2016-12-09 Thread Phil UK
This has been asked by another user today. is there any movement on this
at all as it has been set to confirmed a few months ago now.

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

Title:
  Unable to add time & date stamps to photos

Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Currently there is no setting to allow the time and date stamp to be
  added to photos taken using the camera in Ubuntu Touch.

  This functionality into the camera app should be standard.

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

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


[Touch-packages] [Bug 1648914] [NEW] Add xauth for helping X forwarding scenarios

2016-12-09 Thread Kris
Public bug reported:

Mir is separate from X so it seems counter intuitive to request xauth
added. But let me explain.

Even despite that Ubuntu Touch on devices like phones and tablets lacks
the X stack almost entirely (except mir and what seems to be modified
version of gtk-x11 libs), yet the X forwarding via ssh is a viable
scenario for the same device, even so. Because the X stack from the
remote client will provide the display and input.

Now, I myself am using X forwarding with Ubuntu Touch phone (Meizu MX4)
and I run Gtk apps using this method. The ONLY step I had to was
creating .Xauthority file. That is the only requirement, everything else
is ready for the scenario. The easiest way to generated .Xauthority fule
is with xauth tool. This is also a very light (sizewise) package, so I
think it would be of great benefit.

Optionally, I would see it of further help if possibly upon setting up account 
in newly installed Ubuntu Touch with only Mir, the .Xauthority could be 
auto-generated in the user's home.
Because Mir and X forwarding via ssh do not conflict, they are not mutually 
exclusive.

1. These changes are of tiny footprint yet improve usability greatly
2. Users who build chroot containers will also benefit, being able to copy 
.Xauthority into the chroot so that when inside they can still instantinate X 
forwarded apps

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

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

Title:
  Add xauth for helping X forwarding scenarios

Status in mir package in Ubuntu:
  New

Bug description:
  Mir is separate from X so it seems counter intuitive to request xauth
  added. But let me explain.

  Even despite that Ubuntu Touch on devices like phones and tablets
  lacks the X stack almost entirely (except mir and what seems to be
  modified version of gtk-x11 libs), yet the X forwarding via ssh is a
  viable scenario for the same device, even so. Because the X stack from
  the remote client will provide the display and input.

  Now, I myself am using X forwarding with Ubuntu Touch phone (Meizu
  MX4) and I run Gtk apps using this method. The ONLY step I had to was
  creating .Xauthority file. That is the only requirement, everything
  else is ready for the scenario. The easiest way to generated
  .Xauthority fule is with xauth tool. This is also a very light
  (sizewise) package, so I think it would be of great benefit.

  Optionally, I would see it of further help if possibly upon setting up 
account in newly installed Ubuntu Touch with only Mir, the .Xauthority could be 
auto-generated in the user's home.
  Because Mir and X forwarding via ssh do not conflict, they are not mutually 
exclusive.

  1. These changes are of tiny footprint yet improve usability greatly
  2. Users who build chroot containers will also benefit, being able to copy 
.Xauthority into the chroot so that when inside they can still instantinate X 
forwarded apps

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

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


[Touch-packages] [Bug 1619844] Re: [Xenial] shutdown/reboot hangs at "Reached target Shutdown"

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

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

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

Title:
  [Xenial] shutdown/reboot hangs at "Reached target Shutdown"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I tried getting more information in the debug-shell but I was
  unsuccessful in doing so. I was able to switch to the debug shell via
  ctrl+alt+f9 but I couldn't actually type anything in. I could switch
  back to the stuck shutdown screen via ctrl+alt+f1, and hitting NumLock
  would turn the light on my keyboard on and off, but I couldn't do
  anything else. I captured a journal of the stuck reboot.
  Interestingly, the journal shows a few more lines after "Reached
  target Shutdown", which is as far as I get on my screen.

  This system was installed with Xenial 16.04.1 (never been upgraded)
  and has had this problem since the very first boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Sep  3 00:33:19 2016
  InstallationDate: Installed on 2016-08-17 (16 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5f709fed-48c9-4830-87be-acd13f263eb1 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/mariadb.service → 
/etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-404
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0:

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

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


[Touch-packages] [Bug 1648913] [NEW] Add maliit-inputcontext-gtk3 maliit-inputcontext-gtk2 to default Ubuntu Touch image

2016-12-09 Thread Kris
Public bug reported:

This is a feature request. It is already possible to run Gtk apps directly on 
the phone via XMir, out of the box, on a fresh clean system. However in order 
to enjoy the onscreen keyboard in those applications, it is required to 
manually remount / to writable, install maliit-inputcontext-gtk3 and 
maliit-inputcontext-gtk2 and remount the / back to read-only. 
For an average user this is inconvenient to say the least.

So I would like to ask kindly to just include these two packages in the
default image because:

1. Since running gtk apps is supported (X-Ubuntu-XMir-Enable=true) the osk 
support should be supported out of the box as well
2. These packages both are very very light in size anyways
3. Gtk port for Mir is in works, so this would have it settled ahead of time

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

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

Title:
  Add maliit-inputcontext-gtk3 maliit-inputcontext-gtk2 to default
  Ubuntu Touch image

Status in mir package in Ubuntu:
  New

Bug description:
  This is a feature request. It is already possible to run Gtk apps directly on 
the phone via XMir, out of the box, on a fresh clean system. However in order 
to enjoy the onscreen keyboard in those applications, it is required to 
manually remount / to writable, install maliit-inputcontext-gtk3 and 
maliit-inputcontext-gtk2 and remount the / back to read-only. 
  For an average user this is inconvenient to say the least.

  So I would like to ask kindly to just include these two packages in
  the default image because:

  1. Since running gtk apps is supported (X-Ubuntu-XMir-Enable=true) the osk 
support should be supported out of the box as well
  2. These packages both are very very light in size anyways
  3. Gtk port for Mir is in works, so this would have it settled ahead of time

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

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


[Touch-packages] [Bug 1648911] Re: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package procps is already installed and configured

2016-12-09 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package
  procps is already installed and configured

Status in procps package in Ubuntu:
  New

Bug description:
  i dont know. it will freeze the system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.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
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CrashReports:
   640:0:117:1811831:2016-12-09 16:30:19.293612480 -0800:2016-12-09 
16:30:20.293612480 -0800:/var/crash/libprocps4:amd64.0.crash
   600:0:117:289456:2016-12-09 15:33:26.245213508 -0800:2016-12-09 
15:33:27.245213508 -0800:/var/crash/udev.0.crash
   600:110:117:0:2016-12-09 16:30:35.885889755 -0800:2016-12-09 
16:30:35.885889755 -0800:/var/crash/libprocps4:amd64.0.uploaded
   644:0:117:0:2016-12-09 16:30:28.625485733 -0800:2016-12-09 
16:30:28.625485733 -0800:/var/crash/libprocps4:amd64.0.upload
   600:0:117:289465:2016-12-09 15:33:26.217213392 -0800:2016-12-09 
15:33:27.217213392 -0800:/var/crash/procps.0.crash
  Date: Fri Dec  9 15:33:27 2016
  DuplicateSignature:
   package:procps:2:3.3.10-4ubuntu2.3
   Unpacking thunderbird-locale-en-gb (1:45.5.1+build1-0ubuntu0.16.04.1) ...
   dpkg: error processing package libprocps4:amd64 (--configure):
package libprocps4:amd64 is already installed and configured
  ErrorMessage: package procps is already installed and configured
  InstallationDate: Installed on 2016-12-09 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package 
procps is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1648911] [NEW] package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package procps is already installed and configured

2016-12-09 Thread M Hao
Public bug reported:

i dont know. it will freeze the system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: procps 2:3.3.10-4ubuntu2.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
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CrashReports:
 640:0:117:1811831:2016-12-09 16:30:19.293612480 -0800:2016-12-09 
16:30:20.293612480 -0800:/var/crash/libprocps4:amd64.0.crash
 600:0:117:289456:2016-12-09 15:33:26.245213508 -0800:2016-12-09 
15:33:27.245213508 -0800:/var/crash/udev.0.crash
 600:110:117:0:2016-12-09 16:30:35.885889755 -0800:2016-12-09 
16:30:35.885889755 -0800:/var/crash/libprocps4:amd64.0.uploaded
 644:0:117:0:2016-12-09 16:30:28.625485733 -0800:2016-12-09 16:30:28.625485733 
-0800:/var/crash/libprocps4:amd64.0.upload
 600:0:117:289465:2016-12-09 15:33:26.217213392 -0800:2016-12-09 
15:33:27.217213392 -0800:/var/crash/procps.0.crash
Date: Fri Dec  9 15:33:27 2016
DuplicateSignature:
 package:procps:2:3.3.10-4ubuntu2.3
 Unpacking thunderbird-locale-en-gb (1:45.5.1+build1-0ubuntu0.16.04.1) ...
 dpkg: error processing package libprocps4:amd64 (--configure):
  package libprocps4:amd64 is already installed and configured
ErrorMessage: package procps is already installed and configured
InstallationDate: Installed on 2016-12-09 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: procps
Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package 
procps is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package
  procps is already installed and configured

Status in procps package in Ubuntu:
  New

Bug description:
  i dont know. it will freeze the system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.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
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CrashReports:
   640:0:117:1811831:2016-12-09 16:30:19.293612480 -0800:2016-12-09 
16:30:20.293612480 -0800:/var/crash/libprocps4:amd64.0.crash
   600:0:117:289456:2016-12-09 15:33:26.245213508 -0800:2016-12-09 
15:33:27.245213508 -0800:/var/crash/udev.0.crash
   600:110:117:0:2016-12-09 16:30:35.885889755 -0800:2016-12-09 
16:30:35.885889755 -0800:/var/crash/libprocps4:amd64.0.uploaded
   644:0:117:0:2016-12-09 16:30:28.625485733 -0800:2016-12-09 
16:30:28.625485733 -0800:/var/crash/libprocps4:amd64.0.upload
   600:0:117:289465:2016-12-09 15:33:26.217213392 -0800:2016-12-09 
15:33:27.217213392 -0800:/var/crash/procps.0.crash
  Date: Fri Dec  9 15:33:27 2016
  DuplicateSignature:
   package:procps:2:3.3.10-4ubuntu2.3
   Unpacking thunderbird-locale-en-gb (1:45.5.1+build1-0ubuntu0.16.04.1) ...
   dpkg: error processing package libprocps4:amd64 (--configure):
package libprocps4:amd64 is already installed and configured
  ErrorMessage: package procps is already installed and configured
  InstallationDate: Installed on 2016-12-09 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package 
procps is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1647603] Re: Add option for semi-transparent keyboard

2016-12-09 Thread Kris
So happy to see this feature being added!
About the range, it is a decent range, but I was testing different opacities 
and I thing that 40% is somewhat extreme low value that somehow still makes 
sense in certain scenarios.

Also, I wonder if the very same slider setting could also be available directly 
from the system drop-down menu (sorry don't know the actualname) one where you 
have System, Time & Date, Battery, Sound, etc., there is currently a menu there 
called "Keyboard Layout" that only has one row called "Text Entry Settings...". 
I think it would be great to have the slider there as well, directly, just like 
"Sound" there is a volume slider. Two reasons:
1. The "Keyboard Layout" menu would be less wasteful in the space
2. It would allow for changing opacity without (in staged mode) switching 
context from current window to the window of Settings.

Also, I think that "Keyboard Layout" should be renamed, because:
1. It's long
2. It's missleading. There is no setting about the layout immediately in there. 
There is only further button to go into the "Text Entry Settings...". And with 
transpareny slider added as a 2nd option there, it is also not a Layout per se.

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

Title:
  Add option for semi-transparent keyboard

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request.
  Especially in the landscape mode, the onscreen keyboard takes up a large 
portion of the screen. Potentially it can overlap the window where the text is 
being typed into, so you cannot see what you're typing.
  This could be VERY easily solved by letting users to set transparency level 
for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 
70% opacity on Ubuntu Touch phone, in landscape windowed mode.

  UX fix
  In System settings, the on screen keyboard option will allow a user to set 
the opacity for their OSK.

  This will be a slider in the on screen keyboard option in system
  settings, with the options to set opacity from 50%-100%

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

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


[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-09 Thread Michi Henning
@dobey: There is in the log: terminate called after throwing an instance
of 'unity::scopes::MiddlewareException'

I don't know where this exception comes from. It would be great to find
out. I believe that, if an exception is thrown (no matter what kind of
exception) from one of the threads we send into the scope, the runtime
will handle it correctly. (If not, that's a bug in scopes-api.) But, if
the exception is thrown by a thread that wasn't created by the scopes
runtime, there is obviously nothing much we can do. (In that case, the
other errors are consequential errors, I'd say.)

@mterry: Yes, I did this in side the VM after starting the session.
There is no /run/user/0/dbus-session.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1648909] [NEW] The system is unstable

2016-12-09 Thread 朱昌耀
Public bug reported:

1、Solve the problem about screen cave!
2、Perfect function such as system halt!
3、Improve system interface and make it more beautiful、convenient!

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-31.33-generic 4.8.11
Uname: Linux 4.8.0-31-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
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: Sat Dec 10 08:14:00 2016
DistUpgraded: 2016-11-26 18:10:15,251 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: 
执行子进程“./xorg_fix_proprietary.py”失败(No such file or directory) (8))
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:5040]
InstallationDate: Installed on 2016-11-21 (18 days ago)
InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
MachineType: LENOVO 20C5A08ECD
ProcEnviron:
 LANGUAGE=zh_CN:
 PATH=(custom, no user)
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-31-generic 
root=UUID=03f56536-f682-45a6-8769-4932a6d6cc00 ro locale=zh_CN plymouth:debug=1 
quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2016-11-26 (13 days ago)
dmi.bios.date: 05/20/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ET88WW (2.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C5A08ECD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50518 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET88WW(2.08):bd05/20/2014:svnLENOVO:pn20C5A08ECD:pvrThinkPadEdgeE440:rvnLENOVO:rn20C5A08ECD:rvrSDK0E50518STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C5A08ECD
dmi.product.version: ThinkPad Edge E440
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Sat Dec 10 08:02:07 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


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

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

Title:
  The system is unstable

Status in xorg package in Ubuntu:
  New

Bug description:
  1、Solve the problem about screen cave!
  2、Perfect function such as system halt!
  3、Improve system interface and make it more beautiful、convenient!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-31.33-generic 4.8.11
  Uname: Linux 4.8.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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: Sat Dec 10 08:14:00 2016
  DistUpgraded: 2016-11-26 18:10:15,251 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: 
执行子进程“./xorg_fix_proprietary.py”失败(No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:5040]
  InstallationDate: Installed on 2016-11-21 (18 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20C5A08ECD
  ProcEnviron:
   LANGUAGE=zh_CN:
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  

[Touch-packages] [Bug 1648905] [NEW] VPN username and settings not saved

2016-12-09 Thread dwmw2
Public bug reported:

The OpenConnect VPN auth-dialog doesn't remember usernames and other
settings.

See discussion (and fix) in
https://bugzilla.redhat.com/show_bug.cgi?id=1332491

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

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

Title:
  VPN username and settings not saved

Status in network-manager package in Ubuntu:
  New

Bug description:
  The OpenConnect VPN auth-dialog doesn't remember usernames and other
  settings.

  See discussion (and fix) in
  https://bugzilla.redhat.com/show_bug.cgi?id=1332491

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

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


[Touch-packages] [Bug 893024] Re: Support 802.1x auth requirement detection and fallback

2016-12-09 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Unknown => Confirmed

** Changed in: network-manager
   Importance: Unknown => Wishlist

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

Title:
  Support 802.1x auth requirement detection and fallback

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  NetworkManager asks for 802.1x user name and password when there is no
  802.1x support on switch port.

  Background:

  We use 802.1x wired authentication on our campus network.
  NetworkManager does not fall back nicely when connecting to a non-
  authenticated switch.

  What happens:

  NetworkManager asks for user name and password when "Use 802.1x
  security" is selected in the connection editor and the computer is
  connected to an unauthenticated port.

  What should happen:

  Network manager should notice that the port is not access-controlled
  and do one of the following: (1) ask for connecting unauthenticated or
  (2) connect unauthenticated without asking.

  There should be a setting for selecting #1 or #2.

  Now the user is asked about information which has no effect on
  completing the connection.

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

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


[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

2016-12-09 Thread Dadio
With OTA-14 on a Meizu MX4 and a Audi Car kit.

Progress:
  The phone recognize the Audi Car Kit with the right name (description)
  It is recognised as a headset like with our Peugeot (on which the bluetooth 
works)
  I select the Audi Car Kit and the phone indicates it tries to connect.

Problems:
  The phone doesn't ask for a password
  The phone stops connecting to the Car Kit

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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


[Touch-packages] [Bug 1648901] [NEW] SPNEGO crash on mechanism failure

2016-12-09 Thread dwmw2
Public bug reported:

Chrome (and other things) crash when Kerberos fails to authenticate:
https://bugs.chromium.org/p/chromium/issues/detail?id=554905

This was fixed in MIT krb5 in January:
https://github.com/krb5/krb5/pull/385

Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdd687700 (LWP 14851)]
spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, 
src_name=0x7fffdd685670, targ_name=0x7fffdd685668, 
lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
2315../../../../src/lib/gssapi/spnego/spnego_mech.c: No such file or 
directory.
(gdb) bt
#0  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668, 
lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
#1  0x7fffef72be54 in gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=, src_name=0x7fffdd685788, 
targ_name=0x7fffdd685750, lifetime_rec=0x7fffdd685738, 
mech_type=0x7fffdd685780, ctx_flags=0x7fffdd685734, 
locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c) at 
../../../../src/lib/gssapi/mechglue/g_inq_context.c:114

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

Title:
  SPNEGO crash on mechanism failure

Status in krb5 package in Ubuntu:
  New

Bug description:
  Chrome (and other things) crash when Kerberos fails to authenticate:
  https://bugs.chromium.org/p/chromium/issues/detail?id=554905

  This was fixed in MIT krb5 in January:
  https://github.com/krb5/krb5/pull/385

  Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffdd687700 (LWP 14851)]
  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, 
src_name=0x7fffdd685670, targ_name=0x7fffdd685668, 
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  2315  ../../../../src/lib/gssapi/spnego/spnego_mech.c: No such file or 
directory.
  (gdb) bt
  #0  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668, 
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  #1  0x7fffef72be54 in gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=, src_name=0x7fffdd685788, 
  targ_name=0x7fffdd685750, lifetime_rec=0x7fffdd685738, 
mech_type=0x7fffdd685780, ctx_flags=0x7fffdd685734, 
locally_initiated=0x7fffdd685730, 
  opened=0x7fffdd68572c) at 
../../../../src/lib/gssapi/mechglue/g_inq_context.c:114

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

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


[Touch-packages] [Bug 1595485] Re: packages to remove from zesty

2016-12-09 Thread LocutusOfBorg
patat [armhf] has been removed in Debian too

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

Title:
  packages to remove from zesty

Status in bino package in Ubuntu:
  New
Status in flightgear package in Ubuntu:
  Invalid
Status in fpc package in Ubuntu:
  Fix Released
Status in fslview package in Ubuntu:
  Fix Released
Status in gnome-video-arcade package in Ubuntu:
  Fix Released
Status in insighttoolkit package in Ubuntu:
  Fix Released
Status in insighttoolkit4 package in Ubuntu:
  Invalid
Status in iva package in Ubuntu:
  Fix Released
Status in ldc package in Ubuntu:
  Invalid
Status in libpng package in Ubuntu:
  Fix Released
Status in mame package in Ubuntu:
  Fix Released
Status in patat package in Ubuntu:
  New
Status in pepperflashplugin-nonfree package in Ubuntu:
  Fix Released
Status in ppc64-diag package in Ubuntu:
  Fix Released
Status in python-pysam package in Ubuntu:
  Fix Released
Status in runit package in Ubuntu:
  Fix Released
Status in samtools package in Ubuntu:
  Fix Released
Status in simgear package in Ubuntu:
  Invalid
Status in singular package in Ubuntu:
  Fix Released
Status in stacks package in Ubuntu:
  Fix Released
Status in vcmi package in Ubuntu:
  Fix Released
Status in vmtk package in Ubuntu:
  Fix Released
Status in vtk package in Ubuntu:
  Fix Released
Status in fpc package in Debian:
  Fix Released

Bug description:
  bino [arm64]
  patat [armhf]

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

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


[Touch-packages] [Bug 1595485] Re: packages to remove from zesty

2016-12-09 Thread LocutusOfBorg
bino is sad on arm64, and the reason seems qt-related, I don't think we
should wait for it to be fixed, I want to decruft the old lirc libraries

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

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

** Description changed:

- (NOTE: all of them are gone from Debian)
- 1) libpng.
- Superseded by libpng16
- 
- no reverse dependencies I can see
- 2) insighttoolkit
- Superseded by insighttoolkit4
- it doesn't build on powerpc, so we have to remove binaries here
- (sorry, but Debian maintains only amd64 and i386, and we can't maintain all 
the others including powerpc)
- 
- just removing vmtk/powerpc should allow its removal too
- 
- 3) vtk
- Superseded by vtk6
- 
- needs vmtk migration
- and fslview removal or demote to proposed.
- Debian broke it, because it is already broken, and it has little fix in time 
probability
- (probably we will remove in Debian soon)
- 
- 4) samtools
- old binaries left on armhf: libbam-dev, samtools (from 0.1.19-1ubuntu1)
- old binaries left on powerpc: libbam-dev, samtools (from 0.1.19-1ubuntu1)
- old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1)
- 
- removed in Debian too
- 
- 5) pepperflashplugin-nonfree [i386]
- please remove on i386 (removed in Debian too)
- upstream is not supporting it, so it can't be downloaded/installed on i386 
anymore
- 
- 6) singular [armhf]
- removed in Debian too
- 
- 7) fpc [powerpc]
- powerpc sadness with glib 2.23
- https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480
- 
- 8) mame [ppc64el]
- sandness on that arch, removed in Debian
- 
- 9) flightgear [armhf]
- I don't care about simgear/armhf, because it is unlikely for such a game to 
run on thar architecture.
+ bino [arm64]

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

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

** Description changed:

  bino [arm64]
+ patat [armhf]

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

Title:
  packages to remove from zesty

Status in bino package in Ubuntu:
  New
Status in flightgear package in Ubuntu:
  Invalid
Status in fpc package in Ubuntu:
  Fix Released
Status in fslview package in Ubuntu:
  Fix Released
Status in gnome-video-arcade package in Ubuntu:
  Fix Released
Status in insighttoolkit package in Ubuntu:
  Fix Released
Status in insighttoolkit4 package in Ubuntu:
  Invalid
Status in iva package in Ubuntu:
  Fix Released
Status in ldc package in Ubuntu:
  Invalid
Status in libpng package in Ubuntu:
  Fix Released
Status in mame package in Ubuntu:
  Fix Released
Status in patat package in Ubuntu:
  New
Status in pepperflashplugin-nonfree package in Ubuntu:
  Fix Released
Status in ppc64-diag package in Ubuntu:
  Fix Released
Status in python-pysam package in Ubuntu:
  Fix Released
Status in runit package in Ubuntu:
  Fix Released
Status in samtools package in Ubuntu:
  Fix Released
Status in simgear package in Ubuntu:
  Invalid
Status in singular package in Ubuntu:
  Fix Released
Status in stacks package in Ubuntu:
  Fix Released
Status in vcmi package in Ubuntu:
  Fix Released
Status in vmtk package in Ubuntu:
  Fix Released
Status in vtk package in Ubuntu:
  Fix Released
Status in fpc package in Debian:
  Fix Released

Bug description:
  bino [arm64]
  patat [armhf]

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

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


[Touch-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-12-09 Thread Dave Chiluk
** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

** Changed in: maas-images
   Status: New => Invalid

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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

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


[Touch-packages] [Bug 1648896] [NEW] package hicolor-icon-theme 0.15-1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon

2016-12-09 Thread saxo_zen
Public bug reported:

Crash just after the release update

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: hicolor-icon-theme 0.15-1
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Dec  9 18:57:07 2016
Dependencies:
 
ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: hicolor-icon-theme
Title: package hicolor-icon-theme 0.15-1 failed to install/upgrade: bloqué en 
boucle sur le traitement des actions différées (« triggers »), abandon
UpgradeStatus: Upgraded to yakkety on 2016-12-09 (0 days ago)

** Affects: hicolor-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

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

Title:
  package hicolor-icon-theme 0.15-1 failed to install/upgrade: bloqué en
  boucle sur le traitement des actions différées (« triggers »), abandon

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  Crash just after the release update

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: hicolor-icon-theme 0.15-1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec  9 18:57:07 2016
  Dependencies:
   
  ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-1 failed to install/upgrade: bloqué en 
boucle sur le traitement des actions différées (« triggers »), abandon
  UpgradeStatus: Upgraded to yakkety on 2016-12-09 (0 days ago)

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

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


[Touch-packages] [Bug 1648727] Re: Option greeter-user does not work

2016-12-09 Thread nequx
** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => nequx (nequx)

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

Title:
  Option greeter-user does not work

Status in lightdm package in Ubuntu:
  New

Bug description:
  This option will not work.
  I changed this option like this: greeter-user=root
  But when i restarted the computer and started to go under the root user, then 
i could not do it.
  From the second user admin I was able to enter.
  Attached is the log with an error.

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

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


[Touch-packages] [Bug 1648890] [NEW] X Diagnostics

2016-12-09 Thread Liudger
Public bug reported:

After running X Diagnostics I ran in to some reported bugs.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Dec  9 22:34:13 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0212]
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0212]
InstallationDate: Installed on 2016-11-18 (21 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: eMachines eMachines E525
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=d610160c-133b-4da2-b1f5-7fbdfda6271e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2009
dmi.bios.vendor: eMachines
dmi.bios.version: V2.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: eMachines E525
dmi.board.vendor: eMachines
dmi.board.version: V2.06
dmi.chassis.type: 10
dmi.chassis.vendor: eMachines
dmi.chassis.version: V2.06
dmi.modalias: 
dmi:bvneMachines:bvrV2.06:bd08/03/2009:svneMachines:pneMachinesE525:pvrV2.06:rvneMachines:rneMachinesE525:rvrV2.06:cvneMachines:ct10:cvrV2.06:
dmi.product.name: eMachines E525
dmi.product.version: V2.06
dmi.sys.vendor: eMachines
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Dec  9 21:51:50 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4332 
 vendor AUO
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/1648890

Title:
  X Diagnostics

Status in xorg package in Ubuntu:
  New

Bug description:
  After running X Diagnostics I ran in to some reported bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec  9 22:34:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0212]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0212]
  InstallationDate: Installed on 2016-11-18 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: eMachines eMachines E525
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=d610160c-133b-4da2-b1f5-7fbdfda6271e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2009
  dmi.bios.vendor: eMachines
  dmi.bios.version: V2.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: eMachines E525
  dmi.board.vendor: eMachines
  dmi.board.version: V2.06
  

[Touch-packages] [Bug 1550983] Re: Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

2016-12-09 Thread Bug Watch Updater
** Changed in: gtk+3.0 (Debian)
   Status: Unknown => New

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

Title:
  Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

Status in One Hundred Papercuts:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Debian:
  New

Bug description:
  virt-manager fails to start:

  $ virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (cli:256) Launched with 
command line: /usr/share/virt-manager/virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:143) 
virt-manager version: 1.3.2
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:144) 
virtManager import: 
  Couldn't open libGL.so.1: libGL.so.1: cannot open shared object file: No such 
file or directory
  $

  Installing the 'libgl1-mesa-glx' package resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virt-manager 1:1.3.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 19:19:27 2016
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160206)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1626454] Re: can't connect with owncloud calendars

2016-12-09 Thread Ralf Hersel
I have the same problem even after OTA 14:
- medium secure password (just upper/lower case and numbers, no special chars)
- https (unknown DigiCert certificate)
Error message: Invalid host URL

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

Title:
  can't connect with owncloud calendars

Status in Canonical System Image:
  Fix Released
Status in Ubuntu Calendar App:
  New
Status in account-plugins package in Ubuntu:
  Fix Released

Bug description:
  Running my own ownCloud (v9.1.1). Tried to connect Aquarius 4.5 with Calendar 
App
  The httpS certificate is official, up to date and not self-signed
  I use 7 calendars in my ownCloud-calendar-app.
  (yes, username and password is correct)

  This I tried:

  https://mydomain/owncloud/(suggested minimal path on the phone)
  Error message: Invalid username or password

  https://mydomain/owncloud/remote.php/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/   --> (This is the primary caldav 
address suggested by ownCloud calendar-app)
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/
  Error message: Invalid host URL

  
  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/MYCALENDARNAME/
  Error message: Invalid host URL
  --> This direct path to one of my calendars I use for example to connect my 
different calendars with Thunderbird lightning (its working)

  I tried all with and without ending "/"

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

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


[Touch-packages] [Bug 1204579] Re: ufw doesn't support concurrent updates

2016-12-09 Thread Christopher M Luciano
OK great. I will work on this patch.

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

Title:
  ufw doesn't support concurrent updates

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw package in Debian:
  New

Bug description:
  On a server under Ubuntu 12.04 I automatically update firewall rules and I 
unfortunately noticed that if 2 rules are processed at the same time it leads 
to an inconsistent result between iptables and ufw status.
  In fact it can be reproduced using the python script in attachment.

  Before executing this script I didn't have any rules matching the ip 
192.168.254.1 on my computer.
  After a launch iptables takes into acount 464 rules.

  sudo iptables -L -n | grep 192.168.254.1 | wc -l
  464

  It should be 500 rules but the script stressed a lot my system and all rules 
can't be processed by iptables
  sudo ./test_ufw_threads.py
  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.
  [...]

  Anyway, ufw stores only the last updates (in /lib/ufw/user.rules):

  sudo ufw status
  État : actif

  Vers Action Depuis
   -- --
  192.168.254.1 1234/tcp ALLOW   192.168.46.9
  192.168.254.1 1234/tcp ALLOW   192.168.22.10
  192.168.254.1 1234/tcp ALLOW   192.168.32.10
  192.168.254.1 1234/tcp ALLOW   192.168.5.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.9
  192.168.254.1 1234/tcp ALLOW   192.168.40.10
  192.168.254.1 1234/tcp ALLOW   192.168.46.10
  192.168.254.1 1234/tcp ALLOW   192.168.48.10
  192.168.254.1 1234/tcp ALLOW   192.168.42.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.10

  So I can't delete other rules using ufw, I had to directly use iptables.
  In this case I can only delete 10 rules using ufw.
  Could you please handle some kind of lock?

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

-- 
Mailing list: https://launchpad.net/~touch-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 12.04 and 14.04 LTS's version of libavcodec

2016-12-09 Thread James Cameron
I'm having problems playing videos after this fix.  (LP: #1648721)

-- 
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 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Confirmed
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

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/libav/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked

2016-12-09 Thread Pat McGowan
Will leave this open since alf provided a ppa with a possibly more
complete fix per comment #42

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

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

** Changed in: ubuntu-clock-app
   Status: Confirmed => Invalid

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  In Progress
Status in repowerd:
  In Progress
Status in Ubuntu Clock App:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

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

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


[Touch-packages] [Bug 1647982] Re: [Regression]: Krillin gets to a state where OOM starts killing every app (also Dash)

2016-12-09 Thread Pat McGowan
** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

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

Title:
  [Regression]: Krillin gets to a state where OOM starts killing every
  app (also Dash)

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

Bug description:
  Krillin, rc-proposed/bq-aquaris.en, r486

  Description:
  In the last 3 weeks I managed to get myself into a situation where it was 
completely unusable. 
  Basically, every time I started an app (the *only* one currently running), it 
would get killed
  by OOM after a very short amount of time.
  It did not let me do anything, a few seconds after running the app, the OOM 
would kick in and kill it.
  At one point it started killing the Dash as well as it had nothing else to 
kill as no apps were running.

  A reboot fixes it.
  I'm not sure about how to reproduce this yet. Once you get into that 
situation, the only thing you can do seems to be a reboot.

  I experienced this problem about 3 times in the last couple of weeks.
  I already reported it to the Unity8 team when it happened, but it
  seems like the logs I provided were not enough to show the cause of
  the issue.

  The logs show that some processes have really high Virtual Memory Size, 
probably because they link to plenty of shared libraries or load plenty of 
plugins, but it's maybe something we want to keep an eye on...
  See polld and push-client: they have 900+Mb of VSZ, each.

  Evidence of OOM killing Telegram and then the Dash:
  "free -m" was showing 151Mb with no apps running, then when I tried to run 
one, it would get killed.

  Nov 18 11:08:33 ubuntu-phablet kernel: [182604.420249]   Free memory is 
-2912kB above reserved [gfp(0x200da)]
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251867]Killing 'telegram' 
(15175), adj 100,
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251871]   to free 89460kB on 
behalf of 'QSGRenderThread' (15244) because
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251876]   cache 65396kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251881]   Free memory is 
-2820kB above reserved [gfp(0x200da)]

  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542584]select 'unity8-dash' 
(1385), adj 50, size 8384, to kill
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542617]Killing 'unity8-dash' 
(1385), adj 50,
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542623]   to free 33536kB on 
behalf of 'lsb_release' (1428) because
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542629]   cache 65248kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542634]   Free memory is 
-2900kB above reserved [gfp(0x200da)]

  
  TOP RAM EATERS:
  phablet@ubuntu-phablet:~$ ps aux --sort=-%mem | awk 'NR<=20{print $0}'
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  phablet   2998  0.7 13.3 856732 131420 ?   Ssl  Nov14  44:56 unity8 
--mode=full-greeter
  phablet   5292  6.6  9.8 525300 96952 ?Ssl  11:32   0:15 unity8-dash 
--desktop_file_hint=unity8-dash.desktop
  phablet   2163  0.1  1.8  26096 17996 ?Ss   Nov14  11:36 dbus-daemon 
--fork --session --address=unix:abstract=/tmp/dbus-VwsPw6LOmi
  phablet   3706  0.2  1.7 357620 17064 ?Ssl  Nov14  15:48 maliit-server
  phablet   3721  0.1  1.7 935372 16760 ?Ssl  Nov14   6:38 
/usr/bin/account-polld
  phablet   3828  0.0  1.5 219696 15360 ?Sl   Nov14   2:17 
/usr/lib/evolution/evolution-calendar-factory
  phablet   3696  0.0  1.5 137904 15140 ?Ssl  Nov14   4:40 
/usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor
  phablet   3623  0.0  0.9 193676  9592 ?Ssl  Nov14   3:56 
/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service
  phablet   2941  0.0  0.8 146332  8028 ?Ssl  Nov14   0:22 
/usr/lib/arm-linux-gnueabihf/address-book-service/address-book-service
  phablet   3694  0.0  0.8 976116  7904 ?Ssl  Nov14   1:58 
/usr/lib/ubuntu-push-client/ubuntu-push-client
  phablet   2959  0.0  0.6  97412  6836 ?SNov14   1:45 
/usr/bin/history-daemon
  root  1619  0.3  0.4 111084  4624 ?Ssl  Nov14  20:10 
NetworkManager
  phablet   3768  0.0  0.4 394092  4360 ?Ssl  Nov14   1:33 
/usr/lib/arm-linux-gnueabihf/unity-scopes/smartscopesproxy upstart
  phablet  20493  0.0  0.3  52036  3928 ?Sl   11:18   0:00 
/usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service
  phablet   3814  0.0  0.3  63724  

[Touch-packages] [Bug 1648877] [NEW] Wrong include path to sphinx_config.h

2016-12-09 Thread Silvano Sallese
Public bug reported:

Hi,

This bug appears in more than one Ubuntu 16.04.1 system where I install
the libsphinxbase-dev package through apt.

Some include files have wrong path to the sphinx_config.h header file.

When compiling my code, the header files listed below cause to tell that
there is not a sphinx_config.h file (but it's located in
/usr/include/x86_64-linux-gnu/sphinxbase/).

In order to compile my code I had to modify the following .h files under
the /usr/include/x86_64-linux-gnu/sphinxbase/ system path.

The following corrections solved the issue.

In the file /usr/include/x86_64-linux-gnu/sphinxbase/ad.h at line 44
In the file /usr/include/x86_64-linux-gnu/sphinxbase/prim_type.h at line 88
In the file /usr/include/x86_64-linux-gnu/sphinxbase/sbthread.h at line 46

changed from this
  #include 
to this
  #include 

I hope this could help to update the package.
I use sphinxbase on other systems and I hope in the future I don't need to 
touch the system files.

For completeness:
- this is not happening on Ubuntu 14.04.* systems, but I know the versions are 
heavily different.

- Source: 
http://archive.ubuntu.com/ubuntu/pool/universe/s/sphinxbase/sphinxbase_0.8+5prealpha.orig.tar.gz
the files are in /sphinxbase-5prealpha/include/sphinxbase/

- Package: libsphinxbase-dev

- Package version: 0.8+5prealpha-2ubuntu1

Thank you.

Best regards,
 Silvano

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

** Description changed:

  Hi,
  
  This bug appears in more than one Ubuntu 16.04.1 system where I install
  the libsphinxbase-dev package through apt.
  
  Some include files have wrong path to the sphinx_config.h header file.
  
  When compiling my code, the header files listed below cause to tell that
  there is not a sphinx_config.h file (but it's located in
  /usr/include/x86_64-linux-gnu/sphinxbase/).
  
  In order to compile my code I had to modify the following .h files under
  the /usr/include/x86_64-linux-gnu/sphinxbase/ system path.
  
  The following corrections solved the issue.
  
- In the file /usr/include/x86_64-linux-gnu/sphinxbase/ad.h at line 44 
+ In the file /usr/include/x86_64-linux-gnu/sphinxbase/ad.h at line 44
  In the file /usr/include/x86_64-linux-gnu/sphinxbase/prim_type.h at line 88
  In the file /usr/include/x86_64-linux-gnu/sphinxbase/sbthread.h at line 46
  
- changed from this 
-   #include 
+ changed from this
+   #include 
  to this
-   #include 
+   #include 
  
+ I hope this could help to update the package.
+ I use sphinxbase on other systems and I hope in the future I don't need to 
touch the system files.
  
- I hope this could help to update the package. 
- I use sphinxbase on other systems and I hope in the future I don't need to 
touch the system files.
  For completeness:
  - this is not happening on Ubuntu 14.04.* systems, but I know the versions 
are heavily different.
  
- - Source: 
http://archive.ubuntu.com/ubuntu/pool/universe/s/sphinxbase/sphinxbase_0.8+5prealpha.orig.tar.gz
 
+ - Source: 
http://archive.ubuntu.com/ubuntu/pool/universe/s/sphinxbase/sphinxbase_0.8+5prealpha.orig.tar.gz
  the files are in /sphinxbase-5prealpha/include/sphinxbase/
  
  - Package: libsphinxbase-dev
  
  - Package version: 0.8+5prealpha-2ubuntu1
  
- 
  Thank you.
  
  Best regards,
-  Silvano
+  Silvano

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

Title:
  Wrong include path to sphinx_config.h

Status in sphinxbase package in Ubuntu:
  New

Bug description:
  Hi,

  This bug appears in more than one Ubuntu 16.04.1 system where I
  install the libsphinxbase-dev package through apt.

  Some include files have wrong path to the sphinx_config.h header file.

  When compiling my code, the header files listed below cause to tell
  that there is not a sphinx_config.h file (but it's located in
  /usr/include/x86_64-linux-gnu/sphinxbase/).

  In order to compile my code I had to modify the following .h files
  under the /usr/include/x86_64-linux-gnu/sphinxbase/ system path.

  The following corrections solved the issue.

  In the file /usr/include/x86_64-linux-gnu/sphinxbase/ad.h at line 44
  In the file /usr/include/x86_64-linux-gnu/sphinxbase/prim_type.h at line 88
  In the file /usr/include/x86_64-linux-gnu/sphinxbase/sbthread.h at line 46

  changed from this
    #include 
  to this
    #include 

  I hope this could help to update the package.
  I use sphinxbase on other systems and I hope in the future I don't need to 
touch the system files.

  For completeness:
  - this is not happening on Ubuntu 14.04.* systems, but I know the versions 
are heavily different.

  - Source: 
http://archive.ubuntu.com/ubuntu/pool/universe/s/sphinxbase/sphinxbase_0.8+5prealpha.orig.tar.gz
  the files are in /sphinxbase-5prealpha/include/sphinxbase/

  - Package: libsphinxbase-dev

  - Package version: 0.8+5prealpha-2ubuntu1


[Touch-packages] [Bug 1562111] Re: network-manager no longer restarts dnsmasq

2016-12-09 Thread richud
@nivlac: yes, not sure why I added that.


Anyway bug has been fixed now it seems, dnsmasq is now getting correctly 
restarted.

$ pidof dnsmasq
16166 1693 1692
$ systemctl restart NetworkManager
$ pidof dnsmasq
16966 1693 1692

(1692/3 are libvirt, so not restarted)

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

Title:
  network-manager no longer restarts dnsmasq

Status in network-manager package in Ubuntu:
  New

Bug description:
  restarting Network Manager does not have any effect on it's child
  dnsmasq (nor does stopping and starting)

  ubuntu@ubuntu:~$ pidof dnsmasq
  2355
  ubuntu@ubuntu:~$ sudo systemctl restart NetworkManager
  ubuntu@ubuntu:~$ pidof dnsmasq
  2355

  This problem started in 15.10 and still exists in 16.04 beta2 - it
  works as expected in 14.04.

  The upshot is you cannot load any extra dnsmasq configuration set in
  the conf dir /etc/NetworkManager/dnsmasq.d/ because dnsmasq doesn't
  get restarted.

  
  (As a related issue dnsmasq is also running as 'nobody' and I don't think it 
should, Bug #1105493)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 25 18:13:33 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlp4s0  proto static  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s0  proto kernel  scope link  src 192.168.0.107  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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  53d8bcbd-4047-4705-904a-60eef9d821c1  802-3-ethernet   
1458929440  Fri 25 Mar 2016 06:10:40 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --  --
 -- 
   Mosquitoa88863fb-196e-4000-8103-880e0698d514  802-11-wireless  
1458929448  Fri 25 Mar 2016 06:10:48 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  yes wlp4s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
Mosquitoa88863fb-196e-4000-8103-880e0698d514  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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


[Touch-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

2016-12-09 Thread Ren
@Pat, in which release has this bug-id been fixed ? I have just tested OTA-14 
and the issue is still there.
At the same time tell me where can I find information when a bug id is supposed 
to be fixed how to test it on my own phone ?

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Fix Released
Status in repowerd:
  In Progress
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

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

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


[Touch-packages] [Bug 1640290] Re: Update Qt to 5.7.1

2016-12-09 Thread Timo Jyrinki
Qt 5.7.1 is still not released but hopefully everything would be ready
on upstream side by beginning of January. It seems 5.7.1 will still have
regressions compared to 5.6.1, at least https://codereview.qt-
project.org/#/c/177422, hopefully nothing else.

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

Title:
  Update Qt to 5.7.1

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

Bug description:
  Tracking bug.

  https://people.canonical.com/~ubuntu-archive/transitions/html/html
  /qtbase-abi-5-7-1.html

  Debian successfully completed the 5.7 transition.

  Ubuntu PPA to be populated: https://bileto.ubuntu.com/#/ticket/1985
  More information: https://wiki.ubuntu.com/Touch/QtTesting

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

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


[Touch-packages] [Bug 1648866] Re: package systemd 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-12-09 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package systemd 229-4ubuntu12 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  Ran do-release-upgrade to upgrade from 14.04 to 16.04, this bug came
  up and prompted me to report it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Dec  9 13:54:53 2016
  DuplicateSignature: package:systemd:229-4ubuntu12:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-18 (966 days ago)
  InstallationMedia:
   
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  ProcKernelCmdLine: root=LABEL=DOROOT ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.15
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  Title: package systemd 229-4ubuntu12 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-12-09 (0 days ago)
  dmi.bios.date: 11/03/2016
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20161103
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20161103:bd11/03/2016:svnDigitalOcean:pnDroplet:pvr20161103:cvnBochs:ct1:cvr:
  dmi.product.name: Droplet
  dmi.product.version: 20161103
  dmi.sys.vendor: DigitalOcean

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

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


[Touch-packages] [Bug 1648866] [NEW] package systemd 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-12-09 Thread Steven
Public bug reported:

Ran do-release-upgrade to upgrade from 14.04 to 16.04, this bug came up
and prompted me to report it.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu12
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Dec  9 13:54:53 2016
DuplicateSignature: package:systemd:229-4ubuntu12:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-04-18 (966 days ago)
InstallationMedia:
 
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: DigitalOcean Droplet
ProcKernelCmdLine: root=LABEL=DOROOT ro
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.0.1ubuntu2.15
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 
 2 overridden configuration files found.
Title: package systemd 229-4ubuntu12 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-12-09 (0 days ago)
dmi.bios.date: 11/03/2016
dmi.bios.vendor: DigitalOcean
dmi.bios.version: 20161103
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnDigitalOcean:bvr20161103:bd11/03/2016:svnDigitalOcean:pnDroplet:pvr20161103:cvnBochs:ct1:cvr:
dmi.product.name: Droplet
dmi.product.version: 20161103
dmi.sys.vendor: DigitalOcean

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


** Tags: amd64 apport-package third-party-packages uec-images xenial

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

Title:
  package systemd 229-4ubuntu12 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  Ran do-release-upgrade to upgrade from 14.04 to 16.04, this bug came
  up and prompted me to report it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Dec  9 13:54:53 2016
  DuplicateSignature: package:systemd:229-4ubuntu12:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-18 (966 days ago)
  InstallationMedia:
   
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  ProcKernelCmdLine: root=LABEL=DOROOT ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.15
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  Title: package systemd 229-4ubuntu12 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-12-09 (0 days ago)
  dmi.bios.date: 11/03/2016
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20161103
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20161103:bd11/03/2016:svnDigitalOcean:pnDroplet:pvr20161103:cvnBochs:ct1:cvr:
  dmi.product.name: Droplet
  dmi.product.version: 20161103
  dmi.sys.vendor: DigitalOcean

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

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


[Touch-packages] [Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"

2016-12-09 Thread jorgwel
Is it possible to install accountsservice=0.6.40 in Ubuntu 14.04? I'm
having this bug in a machine which I am not authorized to upgrade to a
more recent version.

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

Title:
  Annoying dialog "Authentication is required to change your own user
  data"

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Invalid
Status in policykit-1-gnome package in Ubuntu:
  Invalid
Status in accountsservice source package in Xenial:
  Fix Released

Bug description:
  * Impact

  Sometimes useless "Authentication is required to change your own user
  data" prompts are displayed

  * Test case

  
  $ ssh -X localhost
  $ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
  $ dbus-send --system --print-reply=literal --dest=org.freedesktop.Accounts 
/org/freedesktop/Accounts/User1001 
org.freedesktop.Accounts.User.SetXHasMessages boolean:true

  that shouldn't trigger a prompt

  * Regression potential

  it allows the change to be done without prompting in more cases,
  shouldn't have an impact on cases which were already working

  
  --

  Every few days a dialog pops up saying "Authentication is required to change 
your own user data" with an entry field for a password. If I type my user's 
password the dialog will reappear with an empty entry field. If I click on the 
cross to close the window many times it will be gone, but reappear a few days 
later. I don't know what this window is for and it makes no difference whether 
I close it or leave it. I don't use the gnome keyring.
  This started with Ubuntu 15.04 or maybe with an earlier release, and is still 
there in Ubuntu 15.10, also on machines I did a fresh install.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Please test proposed package

2016-12-09 Thread Robie Basak
Hello LaMont, or anyone else affected,

Accepted isc-dhcp into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.3-5ubuntu12.6 in a few hours, and then in the -proposed
repository.

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
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:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
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)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  
  [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.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [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 1621507] Please test proposed package

2016-12-09 Thread Robie Basak
Hello LaMont, or anyone else affected,

Accepted initramfs-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.122ubuntu8.7 in a few hours, and then in the -proposed
repository.

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
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:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
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)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  
  [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.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

2016-12-09 Thread Robie Basak
Hello LaMont, or anyone else affected,

Accepted open-iscsi into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/open-
iscsi/2.0.873+git0.3b4b4500-14ubuntu3.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: open-iscsi (Ubuntu Xenial)
   Status: Fix Released => In Progress

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: Fix Committed => In Progress

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
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:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
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:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
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)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  
  [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.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [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:

[Touch-packages] [Bug 1648605] Re: Inserted text ends up on a wrong position after clicking in front of the underlined word in text edit field (web browser)

2016-12-09 Thread Bill Filler
** Changed in: ubuntu-keyboard (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Inserted text ends up on a wrong position after clicking in front of
  the underlined word in text edit field (web browser)

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Hello,
  if you edit text in a web browser's text input field (like Gmail) and click 
right in front of the last inserted word (the underlined one with auto 
corrections available) and then start typing the cursor should stay in front of 
the stuff it was put as well as the text inserted to the current cursor 
position. Instead it gets moved after the underlined word and new text inserted 
after as well.

  I am on rc-proposed, MX4 (and I've been experiencing this bug ever
  since auto correction was made available in the web browser)

  Thank you very much for looking into this.

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

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


[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-12-09 Thread luca
it is possible that this bug will be fixed or not ?. Who can you
contact?

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-12-09 Thread luca
è possibile che verrà risolto questo bug o no?. chi si può contattare?

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-12-09 Thread luca
apport information

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment

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

** Changed in: telepathy-mission-control-5 (Ubuntu)
   Status: New => Confirmed

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

Title:
  mission-control should use different paths when in a snap environment

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  Confirmed

Bug description:
  When running confined into a snap environment, mission-control needs
  to use different paths for its files:

  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY':
 No such file or directory
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY':
 No such file or

  Instead of using $SNAP, it probably should use $SNAP_DATA

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

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


[Touch-packages] [Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

2016-12-09 Thread Robie Basak
Hello LaMont, or anyone else affected,

Accepted ifupdown into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.10ubuntu1.2 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: ifupdown (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  Fix Committed
Status in ifupdown source package in Yakkety:
  Fix Released
Status in ifupdown package in Debian:
  New

Bug description:
  === Begin SRU Template ===
  [Impact]
  The systemd networking.service unit will bring down the loopback device (lo)
  when it is stopped.  This behavior differs from the behavior in other
  Ubuntu releases (upstart's networking.conf), where 'lo' is not taken down.

  The problem that was seen was that iscsi root over ipv6 would hang on
  shutdown.  

  [Test Case]
  Test is fairly simple and can be demonstrated in lxc container.
  The key is really that the lo device should not have its link set down
  after stopping networking.service.  So, below:
out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty

  should not show 'empty', but should have LOOPBACK,UP,LOWER in its
  output.

  $ release=yakkety; name=y1
  $ lxc launch ubuntu-daily:$release $name
  $ sleep 10
  $ lxc exec $name /bin/bash

  ## show only things that are up (note output has LOOPBACK,UP,LOWER_UP)
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  ## Stop the service and show lo link is down (no 'UP' or 'LOWER_UP').
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state DOWN mode DEFAULT group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  empty

  ## Now enable proposed, install update, reboot and show.
  % rel=$(lsb_release -sc)
  % echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  sudo tee /etc/apt/sources.list.d/proposed.list
  % sudo apt update -qy && sudo apt install -qy ifupdown  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  
  [Regression Potential]
  Should be pretty low.  zesty and  yakkety-proposed have this.
  Taking down 'lo' is often cause of 

[Touch-packages] [Bug 1647982] Re: [Regression]: Krillin gets to a state where OOM starts killing every app (also Dash)

2016-12-09 Thread Andrea Bernabei
I installed: 
libglib2.0-0-dbg 
evolution-data-server-dbg
libc6-dbg

Here are 2 more stacktraces I saved after a reboot.
I'm not sure the problem triggers when the connection starts failing...
internet was working now, but I still had the same problem.

indicator-datetime-service stays at about 4% memory, eds at 6%, for a
few minutes, during which I see spamming of GetObject calls in dbus-
monitor.

At one point then datetime-service starts allocating memory, and slowly
grows until reaching a limit.

Here are 2 stacktraces I saved while datetime-service was allocating memory:
https://pastebin.canonical.com/173275/
https://pastebin.canonical.com/173276/

After a few minutes, gdb reported that 10 thread exited.
At that point datetime-service stopped allocating.

Hope that helps!

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

Title:
  [Regression]: Krillin gets to a state where OOM starts killing every
  app (also Dash)

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

Bug description:
  Krillin, rc-proposed/bq-aquaris.en, r486

  Description:
  In the last 3 weeks I managed to get myself into a situation where it was 
completely unusable. 
  Basically, every time I started an app (the *only* one currently running), it 
would get killed
  by OOM after a very short amount of time.
  It did not let me do anything, a few seconds after running the app, the OOM 
would kick in and kill it.
  At one point it started killing the Dash as well as it had nothing else to 
kill as no apps were running.

  A reboot fixes it.
  I'm not sure about how to reproduce this yet. Once you get into that 
situation, the only thing you can do seems to be a reboot.

  I experienced this problem about 3 times in the last couple of weeks.
  I already reported it to the Unity8 team when it happened, but it
  seems like the logs I provided were not enough to show the cause of
  the issue.

  The logs show that some processes have really high Virtual Memory Size, 
probably because they link to plenty of shared libraries or load plenty of 
plugins, but it's maybe something we want to keep an eye on...
  See polld and push-client: they have 900+Mb of VSZ, each.

  Evidence of OOM killing Telegram and then the Dash:
  "free -m" was showing 151Mb with no apps running, then when I tried to run 
one, it would get killed.

  Nov 18 11:08:33 ubuntu-phablet kernel: [182604.420249]   Free memory is 
-2912kB above reserved [gfp(0x200da)]
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251867]Killing 'telegram' 
(15175), adj 100,
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251871]   to free 89460kB on 
behalf of 'QSGRenderThread' (15244) because
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251876]   cache 65396kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251881]   Free memory is 
-2820kB above reserved [gfp(0x200da)]

  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542584]select 'unity8-dash' 
(1385), adj 50, size 8384, to kill
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542617]Killing 'unity8-dash' 
(1385), adj 50,
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542623]   to free 33536kB on 
behalf of 'lsb_release' (1428) because
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542629]   cache 65248kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542634]   Free memory is 
-2900kB above reserved [gfp(0x200da)]

  
  TOP RAM EATERS:
  phablet@ubuntu-phablet:~$ ps aux --sort=-%mem | awk 'NR<=20{print $0}'
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  phablet   2998  0.7 13.3 856732 131420 ?   Ssl  Nov14  44:56 unity8 
--mode=full-greeter
  phablet   5292  6.6  9.8 525300 96952 ?Ssl  11:32   0:15 unity8-dash 
--desktop_file_hint=unity8-dash.desktop
  phablet   2163  0.1  1.8  26096 17996 ?Ss   Nov14  11:36 dbus-daemon 
--fork --session --address=unix:abstract=/tmp/dbus-VwsPw6LOmi
  phablet   3706  0.2  1.7 357620 17064 ?Ssl  Nov14  15:48 maliit-server
  phablet   3721  0.1  1.7 935372 16760 ?Ssl  Nov14   6:38 
/usr/bin/account-polld
  phablet   3828  0.0  1.5 219696 15360 ?Sl   Nov14   2:17 
/usr/lib/evolution/evolution-calendar-factory
  phablet   3696  0.0  1.5 137904 15140 ?Ssl  Nov14   4:40 
/usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor
  phablet   3623  0.0  0.9 193676  9592 ?Ssl  Nov14   3:56 
/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service
  phablet   2941  0.0  0.8 146332  8028 ?Ssl  Nov14   0:22 
/usr/lib/arm-linux-gnueabihf/address-book-service/address-book-service
  phablet   3694  0.0  0.8 976116  7904 ?Ssl  Nov14   1:58 
/usr/lib/ubuntu-push-client/ubuntu-push-client
  phablet   2959  0.0  

[Touch-packages] [Bug 1638708] Re: Hardcoded paths in desktop files need to be processed need $SNAP prefixing

2016-12-09 Thread Launchpad Bug Tracker
This bug was fixed in the package indicator-transfer -
0.2+17.04.20161205-0ubuntu1

---
indicator-transfer (0.2+17.04.20161205-0ubuntu1) zesty; urgency=medium

  * Use cmake-extras EnableCoverageReport instead of custom code for
coverage.
  * Load plug-ins from $SNAP path too.
  * Use UAL C++ API to get app info and launch apps. (LP: #1638708)

 -- Rodney Dawes   Mon, 05 Dec 2016 18:03:02
+

** Changed in: indicator-transfer (Ubuntu)
   Status: New => 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/1638708

Title:
  Hardcoded paths in desktop files need to be processed need $SNAP
  prefixing

Status in indicator-application package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Fix Released

Bug description:
  Noticed and reported by mterry in several indicator patches, e.g.
  :

  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

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

-- 
Mailing list: https://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 1451728] Re: [master] kde-config-telepathy-accounts package install error

2016-12-09 Thread Bernard Sabathé
Sorry, I don't understand english...


Le 09/12/2016 à 18:04, Flames_in_Paradise a écrit :
> @ wxl: I've subscribed u to this bug, as it possibly could be tackled
> for 16.04.2 ?
>

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  SRU information
  ===

  [Impact] It's not possible to install KDE and Unity in co-existence
  because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
  plugins" source package, for example 'account-plugin-facebook'.

  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).

  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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


[Touch-packages] [Bug 1639478] Re: Merge with Debian 0.48.0

2016-12-09 Thread Jeremy Bicha
** Attachment added: "updated build log"
   
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1639478/+attachment/4789652/+files/poppler_0.48.0-2ubuntu1_amd64-2016-12-09T17%3A09%3A37Z.build

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

Title:
  Merge with Debian 0.48.0

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  I successfully test-built poppler 0.48 on zesty. I did not test-build
  the rdepends.

  https://people.canonical.com/~ubuntu-
  archive/transitions/html/poppler.html

  I dropped the change to not build-depend on openjpeg2; the (universe)
  build-depends is fine since we do still disable openjpeg2.

  Changes since Ubuntu version 0.44.0-3ubuntu2
  ===

  https://cgit.freedesktop.org/poppler/poppler/tree/NEWS

  poppler (0.48.0-2) unstable; urgency=medium

    * Upload to unstable. (See #839869)
    * autopkgtest: build the qt5 test with -std=c++11, required with Qt5 >= 5.6.
    * Backport upstream commit 5d15a52aade68c618c356fe403ca500e74917ef7 to 
remove
  an extra '%' in an error message of pdfseparate; patch
  upstream_pdfseparate-remove-extra-in-error-message.patch. (Closes: 
#835202)

   -- Pino Toscano   Sat, 05 Nov 2016 08:29:43 +0100

  poppler (0.48.0-1) experimental; urgency=medium

    * New upstream release:
  - fixes UTF-16 decoding of document outline title (Closes: #702082)
  - fixes crashes in PDF documents (Closes: #830565)
    * Rename packages according to the new SONAMEs:
  - libpoppler61 -> libpoppler64
    * Update copyright.
    * Bump the libglib2.0-dev (build-)dependency to 2.41, as noted in the
  upstream build system.
    * Update symbols files.
    * Bump shlibs for libpoppler-cpp0v5 to >= 0.46.0, following the new APIs
  added.
    * Install the GObject introspection data in a multi-arch directory:
  - bump the libgirepository1.0-dev, and gobject-introspection to
    >= 1.42.0-2~, as providing a fixed dh_girepository
  - update gir1.2-poppler-0.18.install
  - mark gir1.2-poppler-0.18 as Multi-Arch: same

   -- Pino Toscano   Sat, 08 Oct 2016 20:14:42 +0200

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

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


[Touch-packages] [Bug 1639478] Re: Merge with Debian 0.48.0

2016-12-09 Thread Jeremy Bicha
I am subscribing ~ubuntu-sponsors now that the gdal transition is done.

** Description changed:

  I successfully test-built poppler 0.48 on zesty. I did not test-build
  the rdepends.
  
- From looking at the transition tracker, I guess we should wait for the
- gdal transition to complete first.
- 
- https://people.canonical.com/~ubuntu-archive/transitions/html/poppler.html
- https://people.canonical.com/~ubuntu-archive/transitions/html/gdal.html
+ https://people.canonical.com/~ubuntu-
+ archive/transitions/html/poppler.html
  
  I dropped the change to not build-depend on openjpeg2; the (universe)
  build-depends is fine since we do still disable openjpeg2.
  
  Changes since Ubuntu version 0.44.0-3ubuntu2
  ===
  
  https://cgit.freedesktop.org/poppler/poppler/tree/NEWS
  
  poppler (0.48.0-2) unstable; urgency=medium
  
    * Upload to unstable. (See #839869)
    * autopkgtest: build the qt5 test with -std=c++11, required with Qt5 >= 5.6.
    * Backport upstream commit 5d15a52aade68c618c356fe403ca500e74917ef7 to 
remove
  an extra '%' in an error message of pdfseparate; patch
  upstream_pdfseparate-remove-extra-in-error-message.patch. (Closes: 
#835202)
  
   -- Pino Toscano   Sat, 05 Nov 2016 08:29:43 +0100
  
  poppler (0.48.0-1) experimental; urgency=medium
  
    * New upstream release:
  - fixes UTF-16 decoding of document outline title (Closes: #702082)
  - fixes crashes in PDF documents (Closes: #830565)
    * Rename packages according to the new SONAMEs:
  - libpoppler61 -> libpoppler64
    * Update copyright.
    * Bump the libglib2.0-dev (build-)dependency to 2.41, as noted in the
  upstream build system.
    * Update symbols files.
    * Bump shlibs for libpoppler-cpp0v5 to >= 0.46.0, following the new APIs
  added.
    * Install the GObject introspection data in a multi-arch directory:
  - bump the libgirepository1.0-dev, and gobject-introspection to
    >= 1.42.0-2~, as providing a fixed dh_girepository
  - update gir1.2-poppler-0.18.install
  - mark gir1.2-poppler-0.18 as Multi-Arch: same
  
   -- Pino Toscano   Sat, 08 Oct 2016 20:14:42 +0200

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

Title:
  Merge with Debian 0.48.0

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  I successfully test-built poppler 0.48 on zesty. I did not test-build
  the rdepends.

  https://people.canonical.com/~ubuntu-
  archive/transitions/html/poppler.html

  I dropped the change to not build-depend on openjpeg2; the (universe)
  build-depends is fine since we do still disable openjpeg2.

  Changes since Ubuntu version 0.44.0-3ubuntu2
  ===

  https://cgit.freedesktop.org/poppler/poppler/tree/NEWS

  poppler (0.48.0-2) unstable; urgency=medium

    * Upload to unstable. (See #839869)
    * autopkgtest: build the qt5 test with -std=c++11, required with Qt5 >= 5.6.
    * Backport upstream commit 5d15a52aade68c618c356fe403ca500e74917ef7 to 
remove
  an extra '%' in an error message of pdfseparate; patch
  upstream_pdfseparate-remove-extra-in-error-message.patch. (Closes: 
#835202)

   -- Pino Toscano   Sat, 05 Nov 2016 08:29:43 +0100

  poppler (0.48.0-1) experimental; urgency=medium

    * New upstream release:
  - fixes UTF-16 decoding of document outline title (Closes: #702082)
  - fixes crashes in PDF documents (Closes: #830565)
    * Rename packages according to the new SONAMEs:
  - libpoppler61 -> libpoppler64
    * Update copyright.
    * Bump the libglib2.0-dev (build-)dependency to 2.41, as noted in the
  upstream build system.
    * Update symbols files.
    * Bump shlibs for libpoppler-cpp0v5 to >= 0.46.0, following the new APIs
  added.
    * Install the GObject introspection data in a multi-arch directory:
  - bump the libgirepository1.0-dev, and gobject-introspection to
    >= 1.42.0-2~, as providing a fixed dh_girepository
  - update gir1.2-poppler-0.18.install
  - mark gir1.2-poppler-0.18 as Multi-Arch: same

   -- Pino Toscano   Sat, 08 Oct 2016 20:14:42 +0200

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

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


[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

2016-12-09 Thread Till Kamppeter
xnox, can you have a look into this?

-- 
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
Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in systemd 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

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


[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

2016-12-09 Thread Flames_in_Paradise
@ wxl: I've subscribed u to this bug, as it possibly could be tackled
for 16.04.2 ?

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  SRU information
  ===

  [Impact] It's not possible to install KDE and Unity in co-existence
  because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
  plugins" source package, for example 'account-plugin-facebook'.

  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).

  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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


[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2016-12-09 Thread Kirill Shustov
I have similar problem

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"

2016-12-09 Thread James Bowery
This may be a bug that appears when using an SSD for swap.  (I just
can't imagine why people would want to use an SSD for swap ;) ).

This reported that the problem appeared with installation of an SSD for
swap:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1582011/comments/6

That's what happened to me as well.

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

Title:
  Swap Failed, Indefinite hang on reboot/shutdown "Reached target
  Shutdown"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This bug has been affecting me since 15.04
  Prior to shutdown I activate debug-shell 'systemctl start debug-shell'
  I have followed bug #1464917 and installed Xenial-proposed with systemd 
229-4ubuntu5 package.  
  I have finally collected shutdown info using vt9.  
  Issues collecting info due to what I believe is a timeout where vt9 is not 
activated when ctl+alt+F9 is pressed.  I was able to collect info in vt9 to 
file "shutdown.text" I appended outputs to file "shutdown.text" the following 
commands in this order:
  systemctl list-jobs >>shutdown.text
  systemctl --failed >>shutdown.text
  uname -a >>shutdown.text
  systemd --version >>shutdown.text
  lsblk >>shutdown.text
  blkid >>shutdown.text
  journalctl -b >>shutdown.text
  systemctl -all >>shutdown.text
  journalctl -xe >>shutdown.text

  After gaining these data I was only able to finish the reboot with the 
alt+Sysrq and REISUB which forces a reboot even when I just want to shutdown
  Each output I separated upon next boot by hand with a line 
# for easier perusing.

  As a workaround for shutdown/reboot I turn swap off, 'sudo swapoff -a
  && systemctl poweroff' or 'sudo swapoff -a && reboot'  which
  occasionally fails if SWAP has more data than available RAM.  In that
  latter case I am left waiting for the hang and then using
  alt+Sysrq+REISUB to reboot then shutdown again immediately upon boot
  before SWAP has a chance to gain data, then I can use any form of
  halt, poweroff or menu to shutdown.

  I have been unable to get answers from AskUbuntu or the above listed
  bug #1464917 "Reached target Shutdown"  I am filing this bug per
  instructions requested in that bug.  Other systemd bugs I have
  researched #788303 Debian bug reports, #2930 Github and #3087 Github.

  Thanks for your time and efforts to help with this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May 15 12:08:34 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2015-06-29 (321 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Sony Corporation VGN-FW250J
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=b010e611-6efb-49a9-bff0-59b9533d659b ro 
resume=UUID=8bcb4169-f5ab-4ab6-b644-23e528088d41 usbcore.autosuspend=-1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (18 days ago)
  dmi.bios.date: 07/25/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1090Y0
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1090Y0:bd07/25/2008:svnSonyCorporation:pnVGN-FW250J:pvrC6011MLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-FW250J
  dmi.product.version: C6011MLK
  dmi.sys.vendor: Sony Corporation

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

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


[Touch-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

2016-12-09 Thread Anupam
Still present after OTA-14. 
I noticed something new today. Got a call on 2016-12-09 at around 15:11 UTC, 
there was not ringtone (but I answered the call). After ~2 minutes (at around 
15:13 UTC), I got a text message but I didn't hear any sound alert. It is not 
like bug #1544477, where *all* SMS and screenshots used to get silent until a 
reboot.


** Attachment added: "media-hub.log"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+attachment/4789650/+files/media-hub.log

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

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

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


[Touch-packages] [Bug 1648026] Re: Ubuntu 16.10: Setting own DNS server via network connection does nothing

2016-12-09 Thread Sebastien Bacher
there are other dns issue reports like bug #1629611

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

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

Title:
  Ubuntu 16.10: Setting own DNS server via network connection does
  nothing

Status in network-manager package in Ubuntu:
  New

Bug description:
  Setting my "Wired connection 1", IPv4 tab:

  Method: Automatic (DHCP) addresses only
  DNS servers: 127.0.0.1  (runs Bind)

  Saved. Restarted (in 16.04 disconnecting, reconnecting would suffice).
  Rebooted even.

  /etc/resolv.conf still points nameserver 127.0.1.1 and doesn't use my
  bind at 127.0.0.1 to resolve.

  This used to work in 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  7 11:08:13 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-28 (8 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev enp3s0  proto static  metric 100 
   169.254.0.0/16 dev enp3s0  scope link  metric 1000 
   192.168.1.0/24 dev enp3s0  proto kernel  scope link  src 192.168.1.26  
metric 100
  IwConfig:
   enp3s0no wireless extensions.
   
   lono 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-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  c7e523fd-a4cc-3e56-94c4-ddea43b1f11c  802-3-ethernet  
1481105052  Sri 07 Pro 2016 11:04:12  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/0  yes enp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp3s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  c7e523fd-a4cc-3e56-94c4-ddea43b1f11c  
/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.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 893024] Re: Support 802.1x auth requirement detection and fallback

2016-12-09 Thread Sebastien Bacher
** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=723084
   Importance: Unknown
   Status: Unknown

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

Title:
  Support 802.1x auth requirement detection and fallback

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  NetworkManager asks for 802.1x user name and password when there is no
  802.1x support on switch port.

  Background:

  We use 802.1x wired authentication on our campus network.
  NetworkManager does not fall back nicely when connecting to a non-
  authenticated switch.

  What happens:

  NetworkManager asks for user name and password when "Use 802.1x
  security" is selected in the connection editor and the computer is
  connected to an unauthenticated port.

  What should happen:

  Network manager should notice that the port is not access-controlled
  and do one of the following: (1) ask for connecting unauthenticated or
  (2) connect unauthenticated without asking.

  There should be a setting for selecting #1 or #2.

  Now the user is asked about information which has no effect on
  completing the connection.

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

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


[Touch-packages] [Bug 1647603] Re: Add option for semi-transparent keyboard

2016-12-09 Thread K1773R
@Femma
 why 50%-100%? cant we have 0%-100%? this way you can have a invisible keyboard 
while still being able to type!

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

Title:
  Add option for semi-transparent keyboard

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request.
  Especially in the landscape mode, the onscreen keyboard takes up a large 
portion of the screen. Potentially it can overlap the window where the text is 
being typed into, so you cannot see what you're typing.
  This could be VERY easily solved by letting users to set transparency level 
for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 
70% opacity on Ubuntu Touch phone, in landscape windowed mode.

  UX fix
  In System settings, the on screen keyboard option will allow a user to set 
the opacity for their OSK.

  This will be a slider in the on screen keyboard option in system
  settings, with the options to set opacity from 50%-100%

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

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


[Touch-packages] [Bug 1506753] Re: keyboard does pop up not after update to r26

2016-12-09 Thread Nick Dedekind
Ivo's bug logged https://bugs.launchpad.net/qtubuntu/+bug/1648842

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

Title:
  keyboard does pop up not after update to r26

Status in Canonical System Image:
  Incomplete
Status in ubuntu-keyboard package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu bq 4.5. Checked with browser, dekko, calendar and system
  settings (changing the pin). Turned the phone off and on.  No change.

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

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


[Touch-packages] [Bug 1647982] Re: [Regression]: Krillin gets to a state where OOM starts killing every app (also Dash)

2016-12-09 Thread Andrea Bernabei
I confirm I can reliably reproduce the problem. I just have to connect
to WiFi and wait for the ipv6 problem to kick, leaving me connected to
the WiFi AP but without an actual internet connection.

I believe you should be able to reproduce it by creating a fake AP, or
connecting the device to your working AP and then unplugging the modem
from the internet

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

Title:
  [Regression]: Krillin gets to a state where OOM starts killing every
  app (also Dash)

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

Bug description:
  Krillin, rc-proposed/bq-aquaris.en, r486

  Description:
  In the last 3 weeks I managed to get myself into a situation where it was 
completely unusable. 
  Basically, every time I started an app (the *only* one currently running), it 
would get killed
  by OOM after a very short amount of time.
  It did not let me do anything, a few seconds after running the app, the OOM 
would kick in and kill it.
  At one point it started killing the Dash as well as it had nothing else to 
kill as no apps were running.

  A reboot fixes it.
  I'm not sure about how to reproduce this yet. Once you get into that 
situation, the only thing you can do seems to be a reboot.

  I experienced this problem about 3 times in the last couple of weeks.
  I already reported it to the Unity8 team when it happened, but it
  seems like the logs I provided were not enough to show the cause of
  the issue.

  The logs show that some processes have really high Virtual Memory Size, 
probably because they link to plenty of shared libraries or load plenty of 
plugins, but it's maybe something we want to keep an eye on...
  See polld and push-client: they have 900+Mb of VSZ, each.

  Evidence of OOM killing Telegram and then the Dash:
  "free -m" was showing 151Mb with no apps running, then when I tried to run 
one, it would get killed.

  Nov 18 11:08:33 ubuntu-phablet kernel: [182604.420249]   Free memory is 
-2912kB above reserved [gfp(0x200da)]
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251867]Killing 'telegram' 
(15175), adj 100,
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251871]   to free 89460kB on 
behalf of 'QSGRenderThread' (15244) because
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251876]   cache 65396kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251881]   Free memory is 
-2820kB above reserved [gfp(0x200da)]

  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542584]select 'unity8-dash' 
(1385), adj 50, size 8384, to kill
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542617]Killing 'unity8-dash' 
(1385), adj 50,
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542623]   to free 33536kB on 
behalf of 'lsb_release' (1428) because
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542629]   cache 65248kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542634]   Free memory is 
-2900kB above reserved [gfp(0x200da)]

  
  TOP RAM EATERS:
  phablet@ubuntu-phablet:~$ ps aux --sort=-%mem | awk 'NR<=20{print $0}'
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  phablet   2998  0.7 13.3 856732 131420 ?   Ssl  Nov14  44:56 unity8 
--mode=full-greeter
  phablet   5292  6.6  9.8 525300 96952 ?Ssl  11:32   0:15 unity8-dash 
--desktop_file_hint=unity8-dash.desktop
  phablet   2163  0.1  1.8  26096 17996 ?Ss   Nov14  11:36 dbus-daemon 
--fork --session --address=unix:abstract=/tmp/dbus-VwsPw6LOmi
  phablet   3706  0.2  1.7 357620 17064 ?Ssl  Nov14  15:48 maliit-server
  phablet   3721  0.1  1.7 935372 16760 ?Ssl  Nov14   6:38 
/usr/bin/account-polld
  phablet   3828  0.0  1.5 219696 15360 ?Sl   Nov14   2:17 
/usr/lib/evolution/evolution-calendar-factory
  phablet   3696  0.0  1.5 137904 15140 ?Ssl  Nov14   4:40 
/usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor
  phablet   3623  0.0  0.9 193676  9592 ?Ssl  Nov14   3:56 
/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service
  phablet   2941  0.0  0.8 146332  8028 ?Ssl  Nov14   0:22 
/usr/lib/arm-linux-gnueabihf/address-book-service/address-book-service
  phablet   3694  0.0  0.8 976116  7904 ?Ssl  Nov14   1:58 
/usr/lib/ubuntu-push-client/ubuntu-push-client
  phablet   2959  0.0  0.6  97412  6836 ?SNov14   1:45 
/usr/bin/history-daemon
  root  1619  0.3  0.4 111084  4624 ?Ssl  Nov14  20:10 
NetworkManager
  phablet   3768  0.0  0.4 394092  4360 ?Ssl  Nov14   1:33 
/usr/lib/arm-linux-gnueabihf/unity-scopes/smartscopesproxy upstart
  phablet  20493  0.0  0.3  52036  3928 ?Sl   11:18   0:00 
/usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service
  phablet   3814 

[Touch-packages] [Bug 1647982] Re: [Regression]: Krillin gets to a state where OOM starts killing every app (also Dash)

2016-12-09 Thread Andrea Bernabei
I managed to reproduce the problem by triggering 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146

i.e. I just connect to the WiFi in London's office, after a few minutes
the device stays connected to the AP but cannot actually access the
internet (ipv6 kernel problems, afaik), so calendar sync starts failing.

At that point, I see dbus-monitor being spammed with events, and the
memory taken by indicator-datetime-service increases until settling at
40-50% of the total memory in "ps", once the spamming ends.

Stacktrace without dbg symbols shows a malloc (as expected), need to try with 
more dbg syms
Thread 1 (Thread 0xb3ed9000 (LWP 2978)):
#0  0xb6897dea in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0xb689995e in malloc () from /lib/arm-linux-gnueabihf/libc.so.6
#2  0xb693 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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

Title:
  [Regression]: Krillin gets to a state where OOM starts killing every
  app (also Dash)

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

Bug description:
  Krillin, rc-proposed/bq-aquaris.en, r486

  Description:
  In the last 3 weeks I managed to get myself into a situation where it was 
completely unusable. 
  Basically, every time I started an app (the *only* one currently running), it 
would get killed
  by OOM after a very short amount of time.
  It did not let me do anything, a few seconds after running the app, the OOM 
would kick in and kill it.
  At one point it started killing the Dash as well as it had nothing else to 
kill as no apps were running.

  A reboot fixes it.
  I'm not sure about how to reproduce this yet. Once you get into that 
situation, the only thing you can do seems to be a reboot.

  I experienced this problem about 3 times in the last couple of weeks.
  I already reported it to the Unity8 team when it happened, but it
  seems like the logs I provided were not enough to show the cause of
  the issue.

  The logs show that some processes have really high Virtual Memory Size, 
probably because they link to plenty of shared libraries or load plenty of 
plugins, but it's maybe something we want to keep an eye on...
  See polld and push-client: they have 900+Mb of VSZ, each.

  Evidence of OOM killing Telegram and then the Dash:
  "free -m" was showing 151Mb with no apps running, then when I tried to run 
one, it would get killed.

  Nov 18 11:08:33 ubuntu-phablet kernel: [182604.420249]   Free memory is 
-2912kB above reserved [gfp(0x200da)]
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251867]Killing 'telegram' 
(15175), adj 100,
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251871]   to free 89460kB on 
behalf of 'QSGRenderThread' (15244) because
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251876]   cache 65396kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251881]   Free memory is 
-2820kB above reserved [gfp(0x200da)]

  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542584]select 'unity8-dash' 
(1385), adj 50, size 8384, to kill
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542617]Killing 'unity8-dash' 
(1385), adj 50,
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542623]   to free 33536kB on 
behalf of 'lsb_release' (1428) because
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542629]   cache 65248kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542634]   Free memory is 
-2900kB above reserved [gfp(0x200da)]

  
  TOP RAM EATERS:
  phablet@ubuntu-phablet:~$ ps aux --sort=-%mem | awk 'NR<=20{print $0}'
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  phablet   2998  0.7 13.3 856732 131420 ?   Ssl  Nov14  44:56 unity8 
--mode=full-greeter
  phablet   5292  6.6  9.8 525300 96952 ?Ssl  11:32   0:15 unity8-dash 
--desktop_file_hint=unity8-dash.desktop
  phablet   2163  0.1  1.8  26096 17996 ?Ss   Nov14  11:36 dbus-daemon 
--fork --session --address=unix:abstract=/tmp/dbus-VwsPw6LOmi
  phablet   3706  0.2  1.7 357620 17064 ?Ssl  Nov14  15:48 maliit-server
  phablet   3721  0.1  1.7 935372 16760 ?Ssl  Nov14   6:38 
/usr/bin/account-polld
  phablet   3828  0.0  1.5 219696 15360 ?Sl   Nov14   2:17 
/usr/lib/evolution/evolution-calendar-factory
  phablet   3696  0.0  1.5 137904 15140 ?Ssl  Nov14   4:40 
/usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor
  phablet   3623  0.0  0.9 193676  9592 ?Ssl  Nov14   3:56 
/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service
  phablet   2941  0.0  0.8 146332  8028 ?Ssl  Nov14   0:22 

[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-09 Thread Rodney Dawes
Michi, in that scope-registry.log you pastebinned, it looks like the ZMQ
socket is getting closed/removed in the middle of calling Query in the
scope:

(process:2658): ubuntu-app-launch-DEBUG: Initialized Click DB
[2016-12-09 05:20:22.797] ERROR: clickscope: ObjectAdapter: error unmarshaling 
request header (id: , adapter: clickscope-c, op: ): ZmqReceiver::receive(): 
socket was closed

[2016-12-09 05:20:22.807] ERROR: clickscope: ReplyImpl::error(): 
unity::scopes::MiddlewareException: Cannot invoke operations while middleware 
is stopped

I'm not sure why this would happen, and I didn't realize we need to
handle exceptions in the middleware, within the scope itself. Any idea
why the socket would be getting destroyed from the other end? This seems
to be why the scope is blank.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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


[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

2016-12-09 Thread Bug Watch Updater
** Changed in: resolvconf (Debian)
   Status: Unknown => New

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in resolvconf source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Fix Committed
Status in cloud-init source package in Yakkety:
  New
Status in resolvconf source package in Yakkety:
  In Progress
Status in systemd source package in Yakkety:
  Fix Committed
Status in resolvconf package in Debian:
  New

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

  SRU INFORMATION FOR systemd
  ===
  Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and 
(for xenial 

[Touch-packages] [Bug 1647982] Re: [Regression]: Krillin gets to a state where OOM starts killing every app (also Dash)

2016-12-09 Thread Pat McGowan
** Also affects: indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: canonical-devices-system-image
 Assignee: Pat McGowan (pat-mcgowan) => 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/1647982

Title:
  [Regression]: Krillin gets to a state where OOM starts killing every
  app (also Dash)

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

Bug description:
  Krillin, rc-proposed/bq-aquaris.en, r486

  Description:
  In the last 3 weeks I managed to get myself into a situation where it was 
completely unusable. 
  Basically, every time I started an app (the *only* one currently running), it 
would get killed
  by OOM after a very short amount of time.
  It did not let me do anything, a few seconds after running the app, the OOM 
would kick in and kill it.
  At one point it started killing the Dash as well as it had nothing else to 
kill as no apps were running.

  A reboot fixes it.
  I'm not sure about how to reproduce this yet. Once you get into that 
situation, the only thing you can do seems to be a reboot.

  I experienced this problem about 3 times in the last couple of weeks.
  I already reported it to the Unity8 team when it happened, but it
  seems like the logs I provided were not enough to show the cause of
  the issue.

  The logs show that some processes have really high Virtual Memory Size, 
probably because they link to plenty of shared libraries or load plenty of 
plugins, but it's maybe something we want to keep an eye on...
  See polld and push-client: they have 900+Mb of VSZ, each.

  Evidence of OOM killing Telegram and then the Dash:
  "free -m" was showing 151Mb with no apps running, then when I tried to run 
one, it would get killed.

  Nov 18 11:08:33 ubuntu-phablet kernel: [182604.420249]   Free memory is 
-2912kB above reserved [gfp(0x200da)]
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251867]Killing 'telegram' 
(15175), adj 100,
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251871]   to free 89460kB on 
behalf of 'QSGRenderThread' (15244) because
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251876]   cache 65396kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:09:19 ubuntu-phablet kernel: [182650.251881]   Free memory is 
-2820kB above reserved [gfp(0x200da)]

  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542584]select 'unity8-dash' 
(1385), adj 50, size 8384, to kill
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542617]Killing 'unity8-dash' 
(1385), adj 50,
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542623]   to free 33536kB on 
behalf of 'lsb_release' (1428) because
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542629]   cache 65248kB is 
below limit 65536kB for oom_score_adj 12
  Nov 18 11:30:37 ubuntu-phablet kernel: [183928.542634]   Free memory is 
-2900kB above reserved [gfp(0x200da)]

  
  TOP RAM EATERS:
  phablet@ubuntu-phablet:~$ ps aux --sort=-%mem | awk 'NR<=20{print $0}'
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  phablet   2998  0.7 13.3 856732 131420 ?   Ssl  Nov14  44:56 unity8 
--mode=full-greeter
  phablet   5292  6.6  9.8 525300 96952 ?Ssl  11:32   0:15 unity8-dash 
--desktop_file_hint=unity8-dash.desktop
  phablet   2163  0.1  1.8  26096 17996 ?Ss   Nov14  11:36 dbus-daemon 
--fork --session --address=unix:abstract=/tmp/dbus-VwsPw6LOmi
  phablet   3706  0.2  1.7 357620 17064 ?Ssl  Nov14  15:48 maliit-server
  phablet   3721  0.1  1.7 935372 16760 ?Ssl  Nov14   6:38 
/usr/bin/account-polld
  phablet   3828  0.0  1.5 219696 15360 ?Sl   Nov14   2:17 
/usr/lib/evolution/evolution-calendar-factory
  phablet   3696  0.0  1.5 137904 15140 ?Ssl  Nov14   4:40 
/usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor
  phablet   3623  0.0  0.9 193676  9592 ?Ssl  Nov14   3:56 
/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service
  phablet   2941  0.0  0.8 146332  8028 ?Ssl  Nov14   0:22 
/usr/lib/arm-linux-gnueabihf/address-book-service/address-book-service
  phablet   3694  0.0  0.8 976116  7904 ?Ssl  Nov14   1:58 
/usr/lib/ubuntu-push-client/ubuntu-push-client
  phablet   2959  0.0  0.6  97412  6836 ?SNov14   1:45 
/usr/bin/history-daemon
  root  1619  0.3  0.4 111084  4624 ?Ssl  Nov14  20:10 
NetworkManager
  phablet   3768  0.0  0.4 394092  4360 ?Ssl  Nov14   1:33 
/usr/lib/arm-linux-gnueabihf/unity-scopes/smartscopesproxy upstart
  phablet  20493  0.0  0.3  52036  3928 ?Sl   11:18   0:00 
/usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service
  phablet   3814  0.0  0.3  63724  3912 ?Ssl  Nov14   1:14 

[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-12-09 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/indicator-network/indicator-network-
ubuntu-zesty-2275

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Canonical System Image:
  In Progress
Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Released
Status in address-book-service package in Ubuntu:
  Fix Released
Status in camera-app package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  Fix Released
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  In Progress
Status in indicator-location package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-network package in Ubuntu:
  In Progress
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-session package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in maliit-framework package in Ubuntu:
  In Progress
Status in mediaplayer-app package in Ubuntu:
  Fix Released
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  In Progress
Status in unity-scope-scopes package in Ubuntu:
  Won't Fix
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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


[Touch-packages] [Bug 1647603] Re: Add option for semi-transparent keyboard

2016-12-09 Thread Femma
** Description changed:

  OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request.
  Especially in the landscape mode, the onscreen keyboard takes up a large 
portion of the screen. Potentially it can overlap the window where the text is 
being typed into, so you cannot see what you're typing.
  This could be VERY easily solved by letting users to set transparency level 
for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 
70% opacity on Ubuntu Touch phone, in landscape windowed mode.
  
  UX fix
  In System settings, the on screen keyboard option will allow a user to set 
the opacity for their OSK.
+ 
+ This will be a slider in the on screen keyboard option in system
+ settings, with the options to set opacity from 50%-100%

** Changed in: ubuntu-ux
   Status: In Progress => Fix Committed

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

Title:
  Add option for semi-transparent keyboard

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request.
  Especially in the landscape mode, the onscreen keyboard takes up a large 
portion of the screen. Potentially it can overlap the window where the text is 
being typed into, so you cannot see what you're typing.
  This could be VERY easily solved by letting users to set transparency level 
for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 
70% opacity on Ubuntu Touch phone, in landscape windowed mode.

  UX fix
  In System settings, the on screen keyboard option will allow a user to set 
the opacity for their OSK.

  This will be a slider in the on screen keyboard option in system
  settings, with the options to set opacity from 50%-100%

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

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


[Touch-packages] [Bug 1647603] Re: Add option for semi-transparent keyboard

2016-12-09 Thread Femma
** Description changed:

- OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request. 
+ OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request.
  Especially in the landscape mode, the onscreen keyboard takes up a large 
portion of the screen. Potentially it can overlap the window where the text is 
being typed into, so you cannot see what you're typing.
  This could be VERY easily solved by letting users to set transparency level 
for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 
70% opacity on Ubuntu Touch phone, in landscape windowed mode.
+ 
+ UX fix
+ In System settings, the on screen keyboard option will allow a user to set 
the opacity for their OSK.

** Changed in: ubuntu-ux
   Status: New => In Progress

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

Title:
  Add option for semi-transparent keyboard

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request.
  Especially in the landscape mode, the onscreen keyboard takes up a large 
portion of the screen. Potentially it can overlap the window where the text is 
being typed into, so you cannot see what you're typing.
  This could be VERY easily solved by letting users to set transparency level 
for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 
70% opacity on Ubuntu Touch phone, in landscape windowed mode.

  UX fix
  In System settings, the on screen keyboard option will allow a user to set 
the opacity for their OSK.

  This will be a slider in the on screen keyboard option in system
  settings, with the options to set opacity from 50%-100%

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

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


[Touch-packages] [Bug 1648830] [NEW] Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. cat: /var/log/lightdm/x-0-greeter.log.old: File o directory non esistente Gtk-Messag

2016-12-09 Thread bornemao
Public bug reported:

Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
cat: /var/log/lightdm/x-0-greeter.log.old: File o directory non esistente
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
Uname: Linux 4.4.0-46-generic i686
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Dec  9 15:41:39 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller 
[8086:2a12] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated Graphics 
Controller [103c:30d8]
   Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated Graphics 
Controller [103c:30d8]
InstallationDate: Installed on 2015-10-31 (404 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
MachineType: Hewlett-Packard HP Compaq 6720s
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic 
root=UUID=08a9e787-ea51-40ce-88bb-7d0bea6fab28 ro persistenti plymouth:debug 
drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MDU Ver. F.0D
dmi.board.name: 30D8
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 83.0E
dmi.chassis.asset.tag: CNU7513BR7
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MDUVer.F.0D:bd11/04/2008:svnHewlett-Packard:pnHPCompaq6720s:pvrF.0D:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6720s
dmi.product.version: F.0D
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Fri Dec  9 15:37:56 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


** Tags: apport-bug compiz-0.9 i386 ubuntu yakkety

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

Title:
  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged. cat: /var/log/lightdm/x-0-greeter.log.old: File o
  directory non esistente Gtk-Message: GtkDialog mapped without a
  transient parent. This is discouraged.

Status in xorg package in Ubuntu:
  New

Bug description:
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  cat: /var/log/lightdm/x-0-greeter.log.old: File o directory non esistente
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec  9 15:41:39 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller 
[8086:2a12] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:30d8]
 Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:30d8]
  InstallationDate: Installed on 2015-10-31 (404 days ago)
  

[Touch-packages] [Bug 1647603] Re: Add option for semi-transparent keyboard

2016-12-09 Thread Femma
** Changed in: ubuntu-ux
 Assignee: (unassigned) => Femma (femma)

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

Title:
  Add option for semi-transparent keyboard

Status in Ubuntu UX:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request.
  Especially in the landscape mode, the onscreen keyboard takes up a large 
portion of the screen. Potentially it can overlap the window where the text is 
being typed into, so you cannot see what you're typing.
  This could be VERY easily solved by letting users to set transparency level 
for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 
70% opacity on Ubuntu Touch phone, in landscape windowed mode.

  UX fix
  In System settings, the on screen keyboard option will allow a user to set 
the opacity for their OSK.

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

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


[Touch-packages] [Bug 1642593] Re: [rc krillin#69] dialer crashes on close

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  [rc krillin#69] dialer crashes on close

Status in Canonical System Image:
  Fix Released
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  current build number: 69
  device name: krillin
  channel: ubuntu-touch/rc/bq-aquaris.en

  
  Test Case
  1. Launch the dialler
  2. Wait until the UI is fully rendered and close the app from the spread

  Actual result
  It crashes

  Expected result
  It doesn't crash

  https://errors.ubuntu.com/oops/105e7a5a-acc8-11e6-8fd9-fa163ebeb28a
  https://errors.ubuntu.com/oops/d9ebfd8c-acca-11e6-9b33-fa163eec78fa
  https://errors.ubuntu.com/oops/76148854-acc7-11e6-92df-fa163eec78fa

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

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


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

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  Calendar widget gets confused with DST changes

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

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

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

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

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


[Touch-packages] [Bug 1625084] Re: Switching scopes with two fingers on the touchpad doesn't work

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => 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/1625084

Title:
  Switching scopes with two fingers on the touchpad doesn't work

Status in Canonical System Image:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Environment
   
  Product: Freezer HD // Freezer FHD 
  FW version: UBUNTU 15.04 (r14) // UBUNTU 15.04 (r18)
  HW version:  MP
  Material:
   
  Description
   
  Steps to Reproduce:

  1 - Connect DUT to TV by Hdmi.
  2 - Unlock device.
  3 - Try to change between Scopes to the right.

  
  Actual Result:

  You are not able to change between scopes to the right side connected
  to TV by Hdmi, (You cannot change to APP scopes, or desktop app, just
  between Today and Nearby scopes).

  Expected Result:

  You should be able to change between the scopes as expected.
   
  Reproducibility: 100%

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

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


[Touch-packages] [Bug 1626454] Re: can't connect with owncloud calendars

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  can't connect with owncloud calendars

Status in Canonical System Image:
  Fix Released
Status in Ubuntu Calendar App:
  New
Status in account-plugins package in Ubuntu:
  Fix Released

Bug description:
  Running my own ownCloud (v9.1.1). Tried to connect Aquarius 4.5 with Calendar 
App
  The httpS certificate is official, up to date and not self-signed
  I use 7 calendars in my ownCloud-calendar-app.
  (yes, username and password is correct)

  This I tried:

  https://mydomain/owncloud/(suggested minimal path on the phone)
  Error message: Invalid username or password

  https://mydomain/owncloud/remote.php/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/   --> (This is the primary caldav 
address suggested by ownCloud calendar-app)
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/
  Error message: Invalid host URL

  
  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/MYCALENDARNAME/
  Error message: Invalid host URL
  --> This direct path to one of my calendars I use for example to connect my 
different calendars with Thunderbird lightning (its working)

  I tried all with and without ending "/"

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

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


[Touch-packages] [Bug 1622717] Re: "Quit" from quicklist doesn’t close all open windows, doesn’t actually quit the application

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  "Quit" from quicklist doesn’t close all open windows, doesn’t actually
  quit the application

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

Bug description:
  I’m attaching a sample click application that contains a simple qml
  scene that opens several windows. This can be installed on a device
  with:

pkcon install-local --allow-untrusted fubar.osomon_0.4_all.click

  Initially, only one window is open, and tapping on any window opens
  one more window.

  If I reveal the launcher and long press on the app’s icon to select
  the "Quit" option, not all windows are closed:

   - if there is only one window open, it’s closed and the application 
successfully exits
   - if there are two windows open, only the second window is closed, the first 
one remains open (and consequently the application is still running)
   - if there are three windows open, only the first and third one are closed, 
the second one remains…

  Expected behaviour: when "Quit" is tapped, all open windows are
  closed, and the application exits.

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

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


[Touch-packages] [Bug 1623861] Re: Switching between two windows of the same app using quick swipe from right edge breaks focus

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  Switching between two windows of the same app using quick swipe from
  right edge breaks focus

Status in Canonical System Image:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  Switching between two windows of the same app using quick swipe from
  right edge breaks focus.

  What happened:
  1) Install the multi-window version of webbrowser (silo 084)
  2) Open the webbrowser
  3) Focus the address bar, notice that keyboard raises correctly
  3) Spawn a second window
  4) Perform a quick swipe from the right edge to switch back to the first 
window
  5) Focus the address bar and notice that the keyboard doesn't raise

  Note at step 3, sometimes the keyboard does raise and sometimes not
  but after a quick swipe this is always reproducible for me.

  What I expected to happen:
  At step 5) for the keyboard to raise when the focus is given.

  
  When investigating the unity8 log I noticed that when the issue occurs there 
is a second "MirSurface[0x2358780,"webbrowser-app"]::updateActiveFocus() 
unfocused" on the old window after it has given focus to the old window.

  A change window that works: http://pastebin.ubuntu.com/23181435/
  A change window that fails: http://pastebin.ubuntu.com/23181436/

  
  Note a full swipe, which displays the spread, works as expected on my device.

  
  $ apt-cache policy qtmir-android qtubuntu-android webbrowser-app
  qtmir-android:
Installed: 0.4.8+15.04.20160906-0ubuntu1
Candidate: 0.4.8+15.04.20160906-0ubuntu1
Version table:
   *** 0.4.8+15.04.20160906-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.4.4+15.04.20150318-0ubuntu1 0
   50 http://ports.ubuntu.com/ubuntu-ports/ vivid/universe armhf 
Packages
  qtubuntu-android:
Installed: 0.63+15.04.20160912-0ubuntu1
Candidate: 0.63+15.04.20160912-0ubuntu1
Version table:
   *** 0.63+15.04.20160912-0ubuntu1 0
 1001 http://ppa.launchpad.net/ci-train-ppa-service/landing-084/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.63+15.04.20160831-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
   0.60+15.04.20150318-0ubuntu3 0
   50 http://ports.ubuntu.com/ubuntu-ports/ vivid/universe armhf 
Packages
  webbrowser-app:
Installed: 0.23+16.10.20160825-0ubuntu1local~1473859555
Candidate: 0.23+15.04.20160912-0ubuntu1
Version table:
   *** 0.23+16.10.20160825-0ubuntu1local~1473859555 0
  100 /var/lib/dpkg/status
   0.23+15.04.20160912-0ubuntu1 0
 1001 http://ppa.launchpad.net/ci-train-ppa-service/landing-084/ubuntu/ 
vivid/main armhf Packages
   0.23+15.04.20160825-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
   0.23+15.04.20150416-0ubuntu1 0
   50 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

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

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

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


[Touch-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => 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/1588526

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Fix Released
Status in repowerd:
  In Progress
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

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

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


[Touch-packages] [Bug 1594944] Re: Setup.exec() for existing account type results in blank full screen window

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  Setup.exec() for existing account type results in blank full screen
  window

Status in Canonical System Image:
  Fix Released
Status in webapps-sprint:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  If an account already exists, calling Setup.exec() again results in a
  blank window being overlaid on top of the application which made the
  request. There is no way to close this window.

  This API is what the online accounts integration in the scopes API
  relies upon, to allow logging in to accounts, and so we have come to
  rely upon this API as well in multiple places, as a means to log into
  the Ubuntu One account, when it is necessary to do so. However, due to
  this issue, the only way to reliably present a login window at an
  appropriate time, is to delete the account when it appears to have
  been invalidated by the server, and to then present the login window
  to create a new account.

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

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


[Touch-packages] [Bug 1616926] Re: Scrollbar thumb shows as hovered after mouse is released outside the thumb

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  Scrollbar thumb shows as hovered after mouse is released outside the
  thumb

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

Bug description:
  ubuntu-ui-toolkit r2079

  The fix to bug #1608897 created another issue.

  The code that checks if the thumb is being hovered currently only
  checks the y position of the input event, an optimization that worked
  well with the previous assumption that releasing mouse would always
  reset the hover state (but that was causing bug #1608897).

  There were, in fact, 2 cases before:
  - input device moves away (no pressed buttons) -> onExited is fired -> hover 
is reset
  - input device moves away while press-hold is in progress --> onRelease will 
reset hover

  Now that the behaviour changed and release does not reset the hover
  state, we obviously need to check both x and y position

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

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


[Touch-packages] [Bug 1625853] Re: Mouse cursor disappears (or just never changes) when entering the windows of Qt apps

2016-12-09 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  Mouse cursor disappears (or just never changes) when entering the
  windows of Qt apps

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Triaged
Status in MirAL:
  Fix Released
Status in qtubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  To reproduce:
  1) Open qtcreator in mir
  2) Move mouse around window

  Expect:
  Able to see cursor

  Result:
  Cursor goes away as if disabled.

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

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


  1   2   >