[Touch-packages] [Bug 1696402] Re: chroot configuration strictly depends on overlayfs

[Leo Arias]

Thanks Lukasz.

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

Title:
  chroot configuration strictly depends on overlayfs

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released

Bug description:
  The kernel changed the module name from overlayfs to overlay, this
  needs to be taken into consideration when creating the chroot.

  [Impact]

  When trying to create the chroot, it fails like this:
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
  E: 10mount:missing codepage or helper program, or other error
  E: 10mount:
  E: 10mount:In some cases useful info is found in syslog - try
  E: 10mount:dmesg | tail or so.
  E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
  Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
  =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
  ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
  64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
  ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
  UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
  _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
  ERROR

  This makes the autopkgtests fail, so it's blocking bug #1693226.

  [Test Case]

  Run the click autopkgtests.
  Check that there are no errors related to the wrong fs type.

  [Regression Potential]

  Fixing this for artful could make it fail in previous versions.
  However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.

  [Other Info]

  Click is now longer in active development. These tests were failing
  for a long time. In here we are just trying to make a small change on
  the name of the python module so it doesn't conflict with
  python3-click which is in active development and needed by snapcraft
  in bug #1692102.

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

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

[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser

[Leo Arias]

We tested this in xenial, yakkety and zesty proposed, together with snapcraft 
for bug #1692102.
No issues found with the rename of the package, and now snapcraft can be 
updated without problems.

I've just marked this as verified.

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

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  Fix Committed
Status in click source package in Yakkety:
  Fix Committed
Status in click source package in Zesty:
  Fix Committed
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

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

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

[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser

[Leo Arias]

I ran the test cases documented in this bug using a xenial container and
the bileto PPA: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/2812

Everything works as expected.

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  New
Status in click source package in Yakkety:
  New
Status in click source package in Zesty:
  New
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

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

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

[Touch-packages] [Bug 1696402] Re: chroot configuration strictly depends on overlayfs

[Leo Arias]

** Description changed:

  The kernel changed the module name from overlayfs to overlay, this needs
  to be taken into consideration when creating the chroot.
+ 
+ [Impact]
+ 
+ When trying to create the chroot, it fails like this:
+ Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
+ E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
+ E: 10mount:missing codepage or helper program, or other error
+ E: 10mount: 
+ E: 10mount:In some cases useful info is found in syslog - try
+ E: 10mount:dmesg | tail or so.
+ E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
+ Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
+ =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
+ ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
+ 64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
+ ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
+ UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
+ _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
+ ERROR
+ 
+ This makes the autopkgtests fail, so it's blocking #1693226.
+ 
+ [Test Case]
+ 
+ Run the click autopkgtests in artful.
+ Check that there are no errors related to the wrong fs type.
+ 
+ [Regression Potential]
+ 
+ Fixing this for artful could make it fail in previous versions.
+ However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.
+ 
+ [Other Info]
+ 
+ Click is now longer in active development. These tests were failing for
+ a long time. In here we are just trying to make a small change on the
+ name of the python module so it doesn't conflict with python3-click
+ which is in active development and needed by snapcraft in #1692102.

** Description changed:

  The kernel changed the module name from overlayfs to overlay, this needs
  to be taken into consideration when creating the chroot.
  
  [Impact]
  
  When trying to create the chroot, it fails like this:
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
  E: 10mount:missing codepage or helper program, or other error
- E: 10mount: 
+ E: 10mount:
  E: 10mount:In some cases useful info is found in syslog - try
  E: 10mount:dmesg | tail or so.
  E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
  Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
  =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
  ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
  64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
  ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
  UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
  _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
  ERROR
  
- This makes the autopkgtests fail, so it's blocking #1693226.
+ This makes the autopkgtests fail, so it's blocking bug #1693226.
  
  [Test Case]
  
  Run the click autopkgtests in artful.
  Check that there are no errors related to the wrong fs type.
  
  [Regression Potential]
  
  Fixing this for artful could make it fail in previous versions.
  However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.
  
  [Other Info]
  
  Click is now longer in active development. These tests were failing for
  a long time. In here we are just trying to make a small change on the
  name of the python module so it doesn't conflict with python3-click
- which is in

[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser

[Leo Arias]

I ran the test cases documented in this bug using an artful lxc
container.

Everything works as expected.

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

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

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

[Touch-packages] [Bug 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04

[Leo Arias]

** Tags added: trusty

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

Title:
  "system is booting up" while trying to log in after installing snapd
  on ubuntu 14.04

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I've installed snapd on an up-to-date Ubuntu 14.04 server system
  running LTS enablement kernel.

  After toying with snapd and some simple snaps I logged out (so far everything 
was OK).
  I returned to the console after a while (I'm not sure if I logged out but I 
suspect I had to) and I saw the login prompt. After entering my username a line 
was printed "System is booting up" and I was kicked back ot the login prompt 
(It never asked for my password).

  After rebooting the problem went away.

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

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

[Touch-packages] [Bug 892293] Re: Jenkins is not reporting the skipped tests

[Leo Arias]

Wow, this is old. It's surprising that it hasn't been released:

$ apt search python3-junitxml
Sorting... Done
Full Text Search... Done
python3-junitxml/zesty,zesty 0.6-1.1ubuntu1 all
  PyUnit extension for reporting in JUnit compatible XML

I'm no longer using jenkins, and I hope I won't have to use it again. So
this needs a debian bug to ask for the new release.

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

Title:
  Jenkins is not reporting the skipped tests

Status in pyjunitxml:
  Fix Released
Status in pyjunitxml package in Ubuntu:
  New

Bug description:
  We are using junitxml to generate a results file that will be parsed by 
Jenkins for the final reporting.
  The skipped tests are being reported as passed, because they are tagged 
"skip" but Jenkins expects them to be "skipped".

  I couldn't find any specification of the results file, but on [1]
  everything refers to the tag as "skipped".

  [1] http://wiki.apache.org/ant/Proposals/EnhancedTestReports

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

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

[Touch-packages] [Bug 1595558] Re: sudo doesn't have /snap/bin in PATH

[Leo Arias]

I tested this in a trusty lxc. Updated sudo to 1.8.9p5-1ubuntu1.3 and:

# mkdir -p /snap/bin
# cp $(which echo) /snap/bin/echo-test
# su ubuntu
$ sudo echo-test test
test

I'm marking it as verified. Thanks Brian.

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

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

Title:
  sudo doesn't have /snap/bin in PATH

Status in snapd package in Ubuntu:
  Won't Fix
Status in sudo package in Ubuntu:
  Fix Released
Status in snapd source package in Trusty:
  Won't Fix
Status in sudo source package in Trusty:
  Fix Committed
Status in snapd source package in Xenial:
  Won't Fix
Status in sudo source package in Xenial:
  Fix Released

Bug description:
  [ SRU Justification ]
  Snap may contain sysadmin tools as well. They are currently hard to invoke
  because /snap/bin is not in the PATH when sudo is used because the default
  secure_path of sudoers does not have it.

  [ SRU Test Case ]
  1. sudo snap install hello-world
  2. sudo hello-world
  3. verify that this fails with "command not found"
  4. install sudo from xenial-proposed
  5. verify that sudo hello-world now works

  [ Regression Potential ]
  - may trigger conffile prompts on upgrade

  [Original report]
  $ nextcloud.occ
  # prints output

  $ sudo nextcloud.occ
  sudo: nextcloud.occ: command not found

  I need to do `sudo /snap/bin/nextcloud.occ` if I want it to run.

  $ sudo env | grep PATH
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

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

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

[Touch-packages] [Bug 1578007] Re: python-apt in yakkety no longer creates partial

[Leo Arias]

One more time:

Tested in an up-to-date xenial system:
- Enabled the proposed archive
- updated snapcraft to 2.8.8b
- build the mosquitto example.

Works alright. Marking as verification-done.

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

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

Title:
  python-apt in yakkety no longer creates partial

Status in Snapcraft:
  In Progress
Status in python-apt package in Ubuntu:
  In Progress
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Committed

Bug description:
  This now fails: http://paste.ubuntu.com/16208927/
  With an error that looks like http://paste.ubuntu.com/16208917/

  If 'partial' is created in `downloaddir` then it works again

  [Impact]

   * Users of yakkety won't be able to build snaps with stage packages.

   * Users of xenial are not affected.

  [Test Case]

  Build a snap with stage packages:
   * apt get install snapcraft snapcraft-examples
   * mkdir /tmp/mosquitto
   * cp /usr/share/doc/snapcraft-examples/examples/mosquitto/* /tmp/mosquitto
   * cd /tmp/mosquitto
   * snapcraft

  A snap must be generated.

  [Regression Potential]

   * The fix in yakkety could affect the version in xenial.

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

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

[Touch-packages] [Bug 1578007] Re: apt in yakkety no longer creates partial

[Leo Arias]

Tested in an up-to-date xenial system:
- Enabled the proposed archive
- updated snapcraft to 2.8.8a 
- build the mosquitto example.

Works alright.

The fix in the code will work in xenial and yakkety creating the
directory when it's not there, and doing nothing when it is in there.

** Description changed:

  This now fails: http://paste.ubuntu.com/16208927/
  With an error that looks like http://paste.ubuntu.com/16208917/
  
  If 'partial' is created in `downloaddir` then it works again
+ 
+ [Impact]
+ 
+  * Users of yakkety won't be able to build snaps with stage packages.
+ 
+  * Users of xenial are not affected.
+ 
+ [Test Case]
+ 
+ Build a snap with stage packages:
+  * apt get install snapcraft snapcraft-examples
+  * mkdir /tmp/mosquitto
+  * cp /usr/share/doc/snapcraft-examples/examples/mosquitto/* /tmp/mosquitto
+  * cd /tmp/mosquitto
+  * snapcraft
+ 
+ A snap must be generated.
+ 
+ [Regression Potential]
+ 
+  * The fix in yakkety could affect the version in xenial.

** Description changed:

  This now fails: http://paste.ubuntu.com/16208927/
  With an error that looks like http://paste.ubuntu.com/16208917/
  
  If 'partial' is created in `downloaddir` then it works again
  
  [Impact]
  
-  * Users of yakkety won't be able to build snaps with stage packages.
+  * Users of yakkety won't be able to build snaps with stage packages.
  
-  * Users of xenial are not affected.
+  * Users of xenial are not affected.
  
  [Test Case]
  
  Build a snap with stage packages:
-  * apt get install snapcraft snapcraft-examples
-  * mkdir /tmp/mosquitto
-  * cp /usr/share/doc/snapcraft-examples/examples/mosquitto/* /tmp/mosquitto
-  * cd /tmp/mosquitto
-  * snapcraft
+  * apt get install snapcraft snapcraft-examples
+  * mkdir /tmp/mosquitto
+  * cp /usr/share/doc/snapcraft-examples/examples/mosquitto/* /tmp/mosquitto
+  * cd /tmp/mosquitto
+  * snapcraft
  
  A snap must be generated.
  
  [Regression Potential]
  
-  * The fix in yakkety could affect the version in xenial.
+  * The fix in yakkety could affect the version in xenial.

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

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

Title:
  apt in yakkety no longer creates partial

Status in Snapcraft:
  In Progress
Status in python-apt package in Ubuntu:
  Confirmed
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Committed

Bug description:
  This now fails: http://paste.ubuntu.com/16208927/
  With an error that looks like http://paste.ubuntu.com/16208917/

  If 'partial' is created in `downloaddir` then it works again

  [Impact]

   * Users of yakkety won't be able to build snaps with stage packages.

   * Users of xenial are not affected.

  [Test Case]

  Build a snap with stage packages:
   * apt get install snapcraft snapcraft-examples
   * mkdir /tmp/mosquitto
   * cp /usr/share/doc/snapcraft-examples/examples/mosquitto/* /tmp/mosquitto
   * cd /tmp/mosquitto
   * snapcraft

  A snap must be generated.

  [Regression Potential]

   * The fix in yakkety could affect the version in xenial.

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

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

[Touch-packages] [Bug 1574959] Re: Graphic adduser crashes on username having characters not allowed

[Leo Arias]

Hello Daniel. Thanks for reporting the bug.

Could you please add all the steps to reproduce it?


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

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

Title:
  Graphic adduser crashes on username having characters not allowed

Status in adduser package in Ubuntu:
  Incomplete

Bug description:
  "running '/usr/sbin/adduser' failed: El proceso hijo terminó con el
  código 1"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: adduser 3.113+nmu3ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 25 23:25:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  SourcePackage: adduser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1569573] Re: recent snapd path renames causes apparmor to not load profiles on boot

[Leo Arias]

snappy regression test in https://github.com/ubuntu-core/snappy/pull/932

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

Title:
  recent snapd path renames causes apparmor to not load profiles on boot

Status in Snappy:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  /lib/apparmor/functions has this:
  PROFILES_SNAPPY="/var/lib/snappy/apparmor/profiles"

  The recent snappy path renames move the profiles to
  /var/lib/snapd/apparmor/profiles so now snappy apparmor profiles are
  not loading on boot.

  apparmor needs this change:
  PROFILES_SNAPPY="/var/lib/snapd/apparmor/profiles"

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

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

[Touch-packages] [Bug 1520154] Re: /etc/os-release should contain "codename" (like DISTRIB_CODENAME in lsb_release)

[Leo Arias]

os-release now contains UBUNTU_CODENAME.

ubuntu@localhost:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="16.04 (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
UBUNTU_CODENAME=xenial

I'm marking this as fix released. Ogra, will this trigger the removal of
lsb_release? Or what else should we do now here?

** Changed in: snappy
   Status: Confirmed => Fix Released

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

Title:
  /etc/os-release should contain "codename" (like DISTRIB_CODENAME in
  lsb_release)

Status in Snappy:
  Fix Released
Status in base-files package in Ubuntu:
  Fix Released

Bug description:
  to use os-release instead of lsb_release (which adds a python
  dependency to the snappy image and is effectively duplication of
  functionality) /etc/os-release should contain "codename", since the
  value is needed for various container operations (lxd,docker) to
  obtain images

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

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

[Touch-packages] [Bug 1413410] Re: Unable to match embedded NULLs in unix bind rule for abstract sockets

[Leo Arias]

Hey Jamie, I'm not sure how this affects snappy, and I'm not sure how to 
reproduce it in a snappy system.
I see that a fix was released to apparmor. Is there something messing in the 
snappy side?

** Changed in: snappy
   Status: Confirmed => Incomplete

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

Title:
  Unable to match embedded NULLs in unix bind rule for abstract sockets

Status in AppArmor:
  Fix Released
Status in AppArmor 2.9 series:
  In Progress
Status in Snappy:
  Incomplete
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 14.10, I had this in my logs:
  Jan 21 16:32:30 localhost kernel: [24900.927939] audit: type=1400 
audit(1421879550.441:534): apparmor="DENIED" operation="bind" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=12356 comm="plugin-containe" 
family="unix" sock_type="dgram" protocol=0 requested_mask="bind" 
denied_mask="bind" 
addr="@676F6F676C652D6E61636C2D6F316431323335362D33393100"

  $ aa-decode 
676F6F676C652D6E61636C2D6F316431323335362D33393100
  Decoded: google-nacl-o1d12356-391

  $ aa-decode 676F6F676C652D6E61636C2D6
  Decoded: google-nacl-`

  So I tried the following:
  unix bind type=dgram addr=@google-nacl*,
  unix bind type=dgram addr="@google-nacl*",
  unix bind type=dgram addr=@676F6F676C652D6E61636C2D6*,
  unix bind type=dgram addr="@676F6F676C652D6E61636C2D6*",
  unix bind type=dgram addr=@google-nacl*\\000*,
  unix bind type=dgram 
addr=@google-nacl*[0-9a-zA-Z]\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000{,\\000,\\000\\000},

  
  but none of them match. The best I could do was:
  unix bind type=dgram,

  This is likely going to be important for snappy since snappy will have the 
concept of different coordinating snaps interacting via abstract sockets. What 
is interesting is that this seems to work ok for some things, eg:
  ./lightdm:  unix (bind, listen) type=stream 
addr="@/com/ubuntu/upstart-session/**",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/dbus-*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/.ICE-unix/[0-9]*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/dbus-vfs-daemon/*",
  ./lightdm:  unix (bind, listen) type=stream addr="@guest*",

  Is this something in how firefox is setting up the socket?

  To reproduce, enable the firefox profile, start firefox and try to
  attend a google hangout.

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

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

[Touch-packages] [Bug 1536727] Re: make crashes in xenial lxc

[Leo Arias]

Same version doesn't crash on my real xenial machine.

root@calchas:/home/elopio/workspace/canonical/snapcraft# apt-cache policy make
make:
  Instalita: 4.1-2
  Kandidato: 4.1-2
  Montri la prioritatajn tabelojn
 *** 4.1-2 0
500 http://archive.ubuntu.com/ubuntu/ xenial/main amd64 Packages
100 /var/lib/dpkg/status
root@calchas:/home/elopio/workspace/canonical/snapcraft# make -v
GNU Make 4.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

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

Title:
  make crashes in xenial lxc

Status in make-dfsg package in Ubuntu:
  New

Bug description:
  elopio@ubuntu-trusty-vm:~/build/snapcraft$ sudo -E lxc exec xenial -- bash
  root@xenial:~# make -v
  Segmentation fault (core dumped)

  Here's how I create the container on a trusty machine:

  sudo apt-add-repository -y ppa:ubuntu-lxc/lxd-stable
  sudo apt-get update -qq
  sudo apt-get -o Dpkg::Options::="--force-confnew" -y dist-upgrade
  sudo apt-get install -qq lxd lxcfs
  sudo lxd-images import ubuntu xenial --stream daily --alias ubuntu
  sudo lxc launch ubuntu xenial -c security.privileged=true
  while ! sudo lxc info xenial | grep -q eth0.*IPV4; do sleep 5s; done

  Valgrind log: https://paste.ubuntu.com/14591130/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: make 4.1-2
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: scsi_transport_iscsi veth xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc 
iptable_filter ip_tables x_tables btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c snd_hda_codec_generic bnep snd_hda_intel 
snd_hda_controller snd_hda_codec rfcomm snd_hwdep bluetooth snd_pcm 
snd_seq_midi snd_seq_midi_event iosf_mbi snd_rawmidi snd_seq snd_seq_device 
snd_timer crct10dif_pclmul crc32_pclmul snd ghash_clmulni_intel aesni_intel 
soundcore aes_x86_64 8250_fintek lrw gf128mul i2c_piix4 glue_helper ablk_helper 
qxl ttm drm_kms_helper cryptd serio_raw drm parport_pc ppdev mac_hid lp parport 
psmouse floppy pata_acpi
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  Date: Thu Jan 21 01:22:30 2016
  Dependencies:
   gcc-5-base 5.3.1-6ubuntu2
   libc6 2.21-0ubuntu5
   libgcc1 1:5.3.1-6ubuntu2
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
  SourcePackage: make-dfsg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1536727] [NEW] make crashes in xenial lxc

[Leo Arias]

Public bug reported:

elopio@ubuntu-trusty-vm:~/build/snapcraft$ sudo -E lxc exec xenial -- bash
root@xenial:~# make -v
Segmentation fault (core dumped)

Here's how I create the container on a trusty machine:

sudo apt-add-repository -y ppa:ubuntu-lxc/lxd-stable
sudo apt-get update -qq
sudo apt-get -o Dpkg::Options::="--force-confnew" -y dist-upgrade
sudo apt-get install -qq lxd lxcfs
sudo lxd-images import ubuntu xenial --stream daily --alias ubuntu
sudo lxc launch ubuntu xenial -c security.privileged=true
while ! sudo lxc info xenial | grep -q eth0.*IPV4; do sleep 5s; done

Valgrind log: https://paste.ubuntu.com/14591130/

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: make 4.1-2
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelModules: scsi_transport_iscsi veth xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc 
iptable_filter ip_tables x_tables btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c snd_hda_codec_generic bnep snd_hda_intel 
snd_hda_controller snd_hda_codec rfcomm snd_hwdep bluetooth snd_pcm 
snd_seq_midi snd_seq_midi_event iosf_mbi snd_rawmidi snd_seq snd_seq_device 
snd_timer crct10dif_pclmul crc32_pclmul snd ghash_clmulni_intel aesni_intel 
soundcore aes_x86_64 8250_fintek lrw gf128mul i2c_piix4 glue_helper ablk_helper 
qxl ttm drm_kms_helper cryptd serio_raw drm parport_pc ppdev mac_hid lp parport 
psmouse floppy pata_acpi
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
Date: Thu Jan 21 01:22:30 2016
Dependencies:
 gcc-5-base 5.3.1-6ubuntu2
 libc6 2.21-0ubuntu5
 libgcc1 1:5.3.1-6ubuntu2
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
SourcePackage: make-dfsg
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: make-dfsg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images xenial

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

Title:
  make crashes in xenial lxc

Status in make-dfsg package in Ubuntu:
  New

Bug description:
  elopio@ubuntu-trusty-vm:~/build/snapcraft$ sudo -E lxc exec xenial -- bash
  root@xenial:~# make -v
  Segmentation fault (core dumped)

  Here's how I create the container on a trusty machine:

  sudo apt-add-repository -y ppa:ubuntu-lxc/lxd-stable
  sudo apt-get update -qq
  sudo apt-get -o Dpkg::Options::="--force-confnew" -y dist-upgrade
  sudo apt-get install -qq lxd lxcfs
  sudo lxd-images import ubuntu xenial --stream daily --alias ubuntu
  sudo lxc launch ubuntu xenial -c security.privileged=true
  while ! sudo lxc info xenial | grep -q eth0.*IPV4; do sleep 5s; done

  Valgrind log: https://paste.ubuntu.com/14591130/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: make 4.1-2
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: scsi_transport_iscsi veth xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc 
iptable_filter ip_tables x_tables btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c snd_hda_codec_generic bnep snd_hda_intel 
snd_hda_controller snd_hda_codec rfcomm snd_hwdep bluetooth snd_pcm 
snd_seq_midi snd_seq_midi_event iosf_mbi snd_rawmidi snd_seq snd_seq_device 
snd_timer crct10dif_pclmul crc32_pclmul snd ghash_clmulni_intel aesni_intel 
soundcore aes_x86_64 8250_fintek lrw gf128mul i2c_piix4 glue_helper ablk_helper 
qxl ttm drm_kms_helper cryptd serio_raw drm parport_pc ppdev mac_hid lp parport 
psmouse floppy pata_acpi
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  Date: Thu Jan 21 01:22:30 2016
  Dependencies:
   gcc-5-base 5.3.1-6ubuntu2
   libc6 2.21-0ubuntu5
   libgcc1 1:5.3.1-6ubuntu2
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
  SourcePackage: make-dfsg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1382322] Re: Play in music app button is too small for spanish translation

[Leo Arias]

I kind of disagree. I would blame the UI for assuming that the message it wants 
to tell to the user fits in that small space. From the translator's point of 
view, it's wrong to lose part of the message.
I would say that the right widget for this is not a button.

For now, I've updated the translation. Now it only says: Reproducir ( "play" )
https://translations.launchpad.net/ubuntu/xenial/+source/unity-scope-mediascanner/+pots/unity-scope-mediascanner/es/5/+translate

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

Title:
  Play in music app button is too small for spanish translation

Status in Ubuntu Translations:
  New
Status in Ubuntu UX:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  See the attached image.

  It shows the spanish translation of the "Play in music app" button. It
  doesn't fit so it shows "Play in ap...".

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

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

[Touch-packages] [Bug 1534393] [NEW] package systemd 225-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Leo Arias]

Public bug reported:

I was updating my canonistack machine from wily to xenial.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 225-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Fri Jan 15 00:24:49 2016
DuplicateSignature: package:systemd:225-1ubuntu4:subprocess installed 
post-installation script returned error exit status 1
Ec2AMI: ami-0f3b
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.medium
Ec2Kernel: aki-022a
Ec2Ramdisk: ari-022a
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.1.10
SourcePackage: systemd
Title: package systemd 225-1ubuntu4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to xenial on 2016-01-15 (0 days ago)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.3:cvnBochs:ct1:cvr:
dmi.product.name: OpenStack Nova
dmi.product.version: 2013.2.3
dmi.sys.vendor: OpenStack Foundation

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


** Tags: amd64 apport-package dist-upgrade ec2-images third-party-packages 
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/1534393

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

Status in systemd package in Ubuntu:
  New

Bug description:
  I was updating my canonistack machine from wily to xenial.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  Date: Fri Jan 15 00:24:49 2016
  DuplicateSignature: package:systemd:225-1ubuntu4:subprocess installed 
post-installation script returned error exit status 1
  Ec2AMI: ami-0f3b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.medium
  Ec2Kernel: aki-022a
  Ec2Ramdisk: ari-022a
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: systemd
  Title: package systemd 225-1ubuntu4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2016-01-15 (0 days ago)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.3:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2013.2.3
  dmi.sys.vendor: OpenStack Foundation

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

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

[Touch-packages] [Bug 1474426] Re: systemctl status globbing does not work with .service suffix on version 222

[Leo Arias]

This is not blocking us. We worked it around by using the full service
name.

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

Title:
  systemctl status globbing does not work with .service suffix on
  version 222

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I am writing a test that executes systemctl status docker_docker-
  daemon_*.service to get if the docker service is running.

  This works in systemd 219, the version we have in vivid:

  (amd64)ubuntu@test:~$ systemd --version
  systemd 219
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN
  (amd64)ubuntu@test:~$ systemctl status docker_docker-daemon_*.service
  ● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
 Loaded: loaded 
(/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2015-07-14 14:41:10 UTC; 15min ago
   Main PID: 11860 (docker.start)
 CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
 ├─11860 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
 ├─11868 docker.x86_64 -d -G docker -g 
/var/lib/apps/docker/1.6.1.0...
 └─12664 sleep 2

  On version 222, the version we have in wily it doesn't work:

  (amd64)ubuntu@localhost:~$ systemctl status docker_docker-
  daemon_*.service

  (nothing is returned)
  Changing the * by the version, it works:

  (amd64)ubuntu@localhost:~$ systemctl status 
docker_docker-daemon_1.6.1.002.service
  ● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
 Loaded: loaded 
(/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2015-07-14 14:45:31 UTC; 12min ago
   Main PID: 789 (docker.start)
 CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
 ├─ 789 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
 ├─ 800 docker.x86_64 -d -G docker -g 
/var/lib/apps/docker/1.6.1.00...
 └─1372 sleep 2

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

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

[Touch-packages] [Bug 1363386] Re: Use plural forms where appropriate

[Leo Arias]

Added libusermetrics as affected because I found no documentation or
examples about how to support singular and plural messages.

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

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

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

Title:
  Use plural forms where appropriate

Status in Ubuntu Translations:
  Triaged
Status in libusermetrics package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  Messages in indicator/metrics.cpp like

   "%1 calls made today" 
   "%1 calls received today"
   "%1 text messages received today"
   "%1 text messages sent today"
   "Spent %1 minutes in calls today"

  all need to use plural forms, just like messages "%1 missed call" /
  "%1 missed calls" are using them in indicator/messagingmenu.cpp
  already.

  
  Note that plural forms are required even if you know that there will be more 
than one, since languages like Serbian use the noun form depending on the last 
digit of the number (eg. twenty-one will use the same form as one).

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

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

[Touch-packages] [Bug 1474426] [NEW] systemctl status globbing does not work on version 222

[Leo Arias]

Public bug reported:

I am writing a test that executes systemctl status docker_docker-
daemon_*.service to get if the docker service is running.

This works in systemd 219, the version we have in vivid:

(amd64)ubuntu@test:~$ systemd --version
systemd 219
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN
(amd64)ubuntu@test:~$ systemctl status docker_docker-daemon_*.service
● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
   Loaded: loaded (/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; 
enabled; vendor preset: enabled)
   Active: active (running) since Tue 2015-07-14 14:41:10 UTC; 15min ago
 Main PID: 11860 (docker.start)
   CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
   ├─11860 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
   ├─11868 docker.x86_64 -d -G docker -g /var/lib/apps/docker/1.6.1.0...
   └─12664 sleep 2

On version 222, the version we have in wily it doesn't work:

(amd64)ubuntu@localhost:~$ systemctl status docker_docker-
daemon_*.service

(nothing is returned)
Changing the * by the version, it works:

(amd64)ubuntu@localhost:~$ systemctl status 
docker_docker-daemon_1.6.1.002.service
● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
   Loaded: loaded (/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; 
enabled; vendor preset: enabled)
   Active: active (running) since Tue 2015-07-14 14:45:31 UTC; 12min ago
 Main PID: 789 (docker.start)
   CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
   ├─ 789 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
   ├─ 800 docker.x86_64 -d -G docker -g /var/lib/apps/docker/1.6.1.00...
   └─1372 sleep 2

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

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

Title:
  systemctl status globbing does not work on version 222

Status in systemd package in Ubuntu:
  New

Bug description:
  I am writing a test that executes systemctl status docker_docker-
  daemon_*.service to get if the docker service is running.

  This works in systemd 219, the version we have in vivid:

  (amd64)ubuntu@test:~$ systemd --version
  systemd 219
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN
  (amd64)ubuntu@test:~$ systemctl status docker_docker-daemon_*.service
  ● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
 Loaded: loaded 
(/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2015-07-14 14:41:10 UTC; 15min ago
   Main PID: 11860 (docker.start)
 CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
 ├─11860 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
 ├─11868 docker.x86_64 -d -G docker -g 
/var/lib/apps/docker/1.6.1.0...
 └─12664 sleep 2

  On version 222, the version we have in wily it doesn't work:

  (amd64)ubuntu@localhost:~$ systemctl status docker_docker-
  daemon_*.service

  (nothing is returned)
  Changing the * by the version, it works:

  (amd64)ubuntu@localhost:~$ systemctl status 
docker_docker-daemon_1.6.1.002.service
  ● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
 Loaded: loaded 
(/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2015-07-14 14:45:31 UTC; 12min ago
   Main PID: 789 (docker.start)
 CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
 ├─ 789 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
 ├─ 800 docker.x86_64 -d -G docker -g 
/var/lib/apps/docker/1.6.1.00...
 └─1372 sleep 2

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

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

[Touch-packages] [Bug 1474426] Re: systemctl status globbing does not work on version 222

[Leo Arias]

To test it easily in every machine, try: systemctl status *.mount

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

Title:
  systemctl status globbing does not work on version 222

Status in systemd package in Ubuntu:
  New

Bug description:
  I am writing a test that executes systemctl status docker_docker-
  daemon_*.service to get if the docker service is running.

  This works in systemd 219, the version we have in vivid:

  (amd64)ubuntu@test:~$ systemd --version
  systemd 219
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN
  (amd64)ubuntu@test:~$ systemctl status docker_docker-daemon_*.service
  ● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
 Loaded: loaded 
(/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2015-07-14 14:41:10 UTC; 15min ago
   Main PID: 11860 (docker.start)
 CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
 ├─11860 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
 ├─11868 docker.x86_64 -d -G docker -g 
/var/lib/apps/docker/1.6.1.0...
 └─12664 sleep 2

  On version 222, the version we have in wily it doesn't work:

  (amd64)ubuntu@localhost:~$ systemctl status docker_docker-
  daemon_*.service

  (nothing is returned)
  Changing the * by the version, it works:

  (amd64)ubuntu@localhost:~$ systemctl status 
docker_docker-daemon_1.6.1.002.service
  ● docker_docker-daemon_1.6.1.002.service - The docker app deployment mechanism
 Loaded: loaded 
(/etc/systemd/system/docker_docker-daemon_1.6.1.002.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2015-07-14 14:45:31 UTC; 12min ago
   Main PID: 789 (docker.start)
 CGroup: /system.slice/docker_docker-daemon_1.6.1.002.service
 ├─ 789 /bin/bash /apps/docker/1.6.1.002/bin/docker.start
 ├─ 800 docker.x86_64 -d -G docker -g 
/var/lib/apps/docker/1.6.1.00...
 └─1372 sleep 2

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

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

[Touch-packages] [Bug 1356482] Re: The project is missing the README file

[Leo Arias]

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

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

Title:
  The project is missing the README file

Status in dialer-app:
  Fix Released
Status in Snapcraft:
  New
Status in dialer-app package in Ubuntu:
  Invalid

Bug description:
  The readme file should include at least instructions to:

  - build the project
  - run the project
  - run the tests

  Currently there is no README file, which makes it hard for new people
  to collaborate with this project.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1356482/+subscriptions

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

[Touch-packages] [Bug 1461496] [NEW] initctl start url-dispatcher-update-user does not update the protocols database

[Leo Arias]

Public bug reported:

I want to register a protocol for an application putting it in ~/.config
/url-dispatcher/urls. According to Ted, after running

$ initctl start url-dispatcher-update-user

the url dispatcher database should be updated with the new protocol. But that's 
not working.
It only works if I run /usr/lib/*/url-dispatcher/update-directory with the path 
or my .url-dispatcher file.

To check the database after the update:

echo .quit | sqlite3 -batch -csv -cmd "select urls.protocol,
urls.domainsuffix, configfiles.name from urls, configfiles where
urls.sourcefile = configfiles.rowid;" ~/.cache/url-dispatcher/urls-1.db

Here is the branch where I'm automating this test:
https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/register_url_dispatcher/+merge/260923

** Affects: url-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  initctl start url-dispatcher-update-user does not update the protocols
  database

Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  I want to register a protocol for an application putting it in
  ~/.config/url-dispatcher/urls. According to Ted, after running

  $ initctl start url-dispatcher-update-user

  the url dispatcher database should be updated with the new protocol. But 
that's not working.
  It only works if I run /usr/lib/*/url-dispatcher/update-directory with the 
path or my .url-dispatcher file.

  To check the database after the update:

  echo .quit | sqlite3 -batch -csv -cmd "select urls.protocol,
  urls.domainsuffix, configfiles.name from urls, configfiles where
  urls.sourcefile = configfiles.rowid;" ~/.cache/url-
  dispatcher/urls-1.db

  Here is the branch where I'm automating this test:
  
https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/register_url_dispatcher/+merge/260923

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

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

[Touch-packages] [Bug 1305190] Re: Launch Autopilot fake applications with ubuntu-app-launch

[Leo Arias]

The linked branch uses ubuntu-app-launch everywhere, except for
launching the gallery from source. I'm leaving the bug open so we can
keep track of that work too.

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

Title:
  Launch Autopilot fake applications with ubuntu-app-launch

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  According to saviq: We need to get rid of the desktop_file_hint workaround 
rather sooner than later..
  Autopilot now has helpers to launch the test app with ubuntu app launch, so 
we should use that instead.

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

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

[Touch-packages] [Bug 1305190] Re: Launch Autopilot fake applications with ubuntu-app-launch

[Leo Arias]

** Branch linked: lp:~canonical-platform-qa/ubuntu-ui-toolkit/fix1305190
-ubuntu-app-launch

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

Title:
  Launch Autopilot fake applications with ubuntu-app-launch

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  According to saviq: We need to get rid of the desktop_file_hint workaround 
rather sooner than later..
  Autopilot now has helpers to launch the test app with ubuntu app launch, so 
we should use that instead.

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

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

[Touch-packages] [Bug 1305190] Re: Launch Autopilot fake applications with ubuntu-app-launch

[Leo Arias]

** Summary changed:

- Launch Autopilot fake applications with upstart
+ Launch Autopilot fake applications with ubuntu-app-launch

** Description changed:

  According to saviq: We need to get rid of the desktop_file_hint workaround 
rather sooner than later..
- Autopilot now has helpers to launch the test app with upstart, so we should 
use that instead.
+ Autopilot now has helpers to launch the test app with ubuntu app launch, so 
we should use that instead.

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

Title:
  Launch Autopilot fake applications with ubuntu-app-launch

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  According to saviq: We need to get rid of the desktop_file_hint workaround 
rather sooner than later..
  Autopilot now has helpers to launch the test app with ubuntu app launch, so 
we should use that instead.

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

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

[Touch-packages] [Bug 1356497] Re: Can't make the project in a build dir

[Leo Arias]

The problem is that the make files are written on the root of the
branch, not on the current dir.

elopio@tangamandapio76:~/workspace/canonical/dialer-app/trunk$ mkdir builddir
elopio@tangamandapio76:~/workspace/canonical/dialer-app/trunk$ cd builddir/
elopio@tangamandapio76:~/workspace/canonical/dialer-app/trunk/builddir$ cmake 
..-- Could NOT find Lcov (missing:  LCOV_EXECUTABLE GENHTML_EXECUTABLE) 
-- Could NOT find gcovr (missing:  GCOVR_EXECUTABLE) 
-- Configuring done
-- Generating done
-- Build files have been written to: 
/home/elopio/workspace/canonical/dialer-app/trunk
elopio@tangamandapio76:~/workspace/canonical/dialer-app/trunk/builddir$ make
make: *** No targets specified and no makefile found.  Stop.


** Changed in: dialer-app (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Can't make the project in a build dir

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  cmake is instended to separate the source from the built files, but
  it's currently not possible to make the project in a builddir.

  To reproduce:
  mkdir builddir
  cd builddir
  cmake ..
  make <- fails

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

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

[Touch-packages] [Bug 1446846] Re: Three consistent autopilot test failures

[Leo Arias]

** Branch linked: lp:~canonical-platform-
qa/unity8/fix1446846-test_slider_revert

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

Title:
  Three consistent autopilot test failures

Status in unity8 package in Ubuntu:
  Triaged
Status in unity8 source package in Vivid:
  New

Bug description:
  We seem to have stabilized on three tests failing repeatedly:

  
unity8.indicators.tests.test_action_latency.TestClientRevertsToServerValue.test_slider_reverts_on_late_response(Native
 Device)
  
unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_greeter_hides_on_app_open
  
unity8.indicators.tests.test_action_latency.TestBuffering.test_slider_buffers_activations(Native
 Device)

  Example run:

  https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-
  mako/2076/#showFailuresLink

  The two latency ones are relatively new tests, the lifecycle one seems
  to be a new consistent failure.

  What's even more important is that they're reliably reproducible
  locally using the steps below:

  http://ubuntu-test-cases-touch.readthedocs.org/en/latest/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150409.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 21 22:18:54 2015
  SourcePackage: unity8
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1446846] Re: Three consistent autopilot test failures

[Leo Arias]

unity8.indicators.tests.test_action_latency.TestClientRevertsToServerValue.test_slider_reverts_on_late_response
fails because the wait_for is placed after the finger touch is released.
As the slider reverts the value, if the next statement is not fast
enough it will find the original value instead of the new one.

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

Title:
  Three consistent autopilot test failures

Status in unity8 package in Ubuntu:
  Triaged
Status in unity8 source package in Vivid:
  New

Bug description:
  We seem to have stabilized on three tests failing repeatedly:

  
unity8.indicators.tests.test_action_latency.TestClientRevertsToServerValue.test_slider_reverts_on_late_response(Native
 Device)
  
unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_greeter_hides_on_app_open
  
unity8.indicators.tests.test_action_latency.TestBuffering.test_slider_buffers_activations(Native
 Device)

  Example run:

  https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-
  mako/2076/#showFailuresLink

  The two latency ones are relatively new tests, the lifecycle one seems
  to be a new consistent failure.

  What's even more important is that they're reliably reproducible
  locally using the steps below:

  http://ubuntu-test-cases-touch.readthedocs.org/en/latest/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150409.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 21 22:18:54 2015
  SourcePackage: unity8
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1370791] Re: [system-settings] When brightness is set to automatic, the slider doesn't show current value

[Leo Arias]

@mpt: awesome solution, that would make me very happy.

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

Title:
  [system-settings] When brightness is set to automatic, the slider
  doesn't show current value

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Power Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  On the brightness page, there is a slider to set brightness and a
  checkbox to set it automatically.

  When I select the automatic brightness, I was expecting the slider to
  show the current brightness level. Instead, it just keeps the old
  value manually set. I find this a little confusing: I have a slider
  whose value I can change, but will do nothing while the checkbox is
  marked, and the value it shows is different from the current
  brightness of the screen.

  : "Because users
  have different preferences, the function should also be user-
  adjustable. This should be achieved by altering the display brightness
  manually while 'Adjust automatically' is checked."

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

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

[Touch-packages] [Bug 1454882] [NEW] when swiping the launcher on the tutorial, it leaves the edge

[Leo Arias]

Public bug reported:

When I do the swipe that opens the launcher on the tutorial, the launcher is no 
longer anchored to the left edge.
(take a look at the attached screenshot).

To reproduce:
Flash the phone.
Finish the wizard.
Do the first swipe of the tutorial.

Tested in krillin devel-proposed 210

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

** Attachment added: "Ekrankopio de 2015-05-13 17:38:18.png"
   
https://bugs.launchpad.net/bugs/1454882/+attachment/4397040/+files/Ekrankopio%20de%202015-05-13%2017%3A38%3A18.png

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

Title:
  when swiping the launcher on the tutorial, it leaves the edge

Status in unity8 package in Ubuntu:
  New

Bug description:
  When I do the swipe that opens the launcher on the tutorial, the launcher is 
no longer anchored to the left edge.
  (take a look at the attached screenshot).

  To reproduce:
  Flash the phone.
  Finish the wizard.
  Do the first swipe of the tutorial.

  Tested in krillin devel-proposed 210

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

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

[Touch-packages] [Bug 1452300] Re: Reboot takes too long

[Leo Arias]

Oh, that complicates the test quite a bit. We would need to use ssh
without adb.

Did you find a way to add a regression test at a lower level, or should
we add a manual test for reboots to the release plan?

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

Title:
  Reboot takes too long

Status in the base for Ubuntu mobile products:
  New
Status in powerd package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in powerd source package in Vivid:
  New
Status in powerd package in Ubuntu RTM:
  Fix Released

Bug description:
  Test case.
  - Make sure phone is not plugged in.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="816" x-info="http://w
  ww.rsyslog.com"] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="817" x-info="http://w
  ww.rsyslog.com"] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

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

[Touch-packages] [Bug 1452300] Re: Reboot takes too long

[Leo Arias]

We could write a regression test for this, using the same test vila started to 
check that unity doesn't hang after reboots:
https://code.launchpad.net/~canonical-platform-qa/unity8/1421009-hangs-on-boot/+merge/257408

We can take timestamps before and after the reboot, and see if they meet
a reasonable threshold.

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

Title:
  Reboot takes too long

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="816" x-info="http://w
  ww.rsyslog.com"] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="817" x-info="http://w
  ww.rsyslog.com"] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

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

[Touch-packages] [Bug 1451945] Re: The autopilot documentation for click_element mentions the wrong parameter name

[Leo Arias]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Leo Arias (elopio)

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

Title:
  The autopilot documentation for click_element mentions the wrong
  parameter name

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The right name of the argument is object_name, and the doc mentions
  objectName.

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

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

[Touch-packages] [Bug 1451945] [NEW] The autopilot documentation for click_element mentions the wrong parameter name

[Leo Arias]

Public bug reported:

The right name of the argument is object_name, and the doc mentions
objectName.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Assignee: Leo Arias (elopio)
 Status: In Progress

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

Title:
  The autopilot documentation for click_element mentions the wrong
  parameter name

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The right name of the argument is object_name, and the doc mentions
  objectName.

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

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

[Touch-packages] [Bug 1450494] Re: Unity8 welcome wizard crashes after changing language

[Leo Arias]

The fix in the branch comes with no test. Should we add a regression
test in unity to go forth and back on the wizard pages?

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

Title:
  Unity8 welcome wizard crashes after changing language

Status in qmenumodel package in Ubuntu:
  In Progress

Bug description:
  To reproduce:
  - start the welcome wizard on an Ubuntu Touch phone
  - click 'Continue'
  - click 'Back'
  - change language
  - click 'Continue'
  - click 'Back'

  Repeat those last three steps a few times and you will eventually
  create a crash (usually within 5 tries).

  It is because of a libqmenumodel bug triggered when we restart the
  indicators to force them to notice the new language.

  Below is a stacktrace for the g_variant_unref failure (trying to unref
  a GVariant without any refs, with fatal-criticals turned on).  The
  problem is that GtkMenuTrackerItem tries to unref its stored state
  GVariant on finalize, when it already unref'd it earlier.  Branch
  attached to this bug.

  #0 0x in () at /lib/arm-linux-gnueabihf/libc.so.6
  #1 0x in raise () at /lib/arm-linux-gnueabihf/libc.so.6
  #2 0x in g_logv (breakpoint=1)
  at /build/buildd/glib2.0-2.44.0/./glib/gmessages.c:315
  #3 0x in g_logv (log_domain=0xb5cb1860 "GLib", 
log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=format@entry=0xb39435bc 
 "", args=..., args@entry=...)
  at /build/buildd/glib2.0-2.44.0/./glib/gmessages.c:1041
  #4 0x in g_log (log_domain=, 
log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=0xb5cba5dc "%s: 
assertion '%s' failed")
  at /build/buildd/glib2.0-2.44.0/./glib/gmessages.c:1079
  #5 0x in g_return_if_fail_warning (log_domain=, 
pretty_function=, expression=)
  at /build/buildd/glib2.0-2.44.0/./glib/gmessages.c:1088
  #6 0x in gtk_menu_tracker_item_finalize (object=0x10abae0 
[GtkMenuTrackerItem])
  at 
/build/buildd/qmenumodel-0.2.9+15.04.20150108/libqmenumodel/src/gtk/gtkmenutrackeritem.c:205
  #7 0x in g_object_unref (_object=0x10abae0)
  at /build/buildd/glib2.0-2.44.0/./gobject/gobject.c:3174
  #8 0x in real_node_free (node=0xade173c0, seq=0x10df290)
  at /build/buildd/glib2.0-2.44.0/./glib/gsequence.c:1793
  #9 0x in UnityMenuModel::event(QEvent*) (this=
  ---Type  to continue, or q  to quit---
  0xfa4970, e=)
  at 
/build/buildd/qmenumodel-0.2.9+15.04.20150108/libqmenumodel/src/unitymenumodel.cpp:789
  #10 0x in QCoreApplication::notify(QObject*, QEvent*) ()
  at /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  #11 0x in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
  at /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  #12 0x in UnityMenuModelPrivate::menuItemRemoved(int, void*) 
(event=0xbedfeb04, receiver=)
  at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qcoreapplication.h:237
  #13 0x in UnityMenuModelPrivate::menuItemRemoved(int, void*) 
(position=, user_data=0xc5c160)
  at 
/build/buildd/qmenumodel-0.2.9+15.04.20150108/libqmenumodel/src/unitymenumodel.cpp:260
  #14 0x in gtk_menu_tracker_model_changed (tracker=0xade18b48, 
tracker=0xade18b48, n_items=1, offset=0, change_point=0xade18b34)
  at 
/build/buildd/qmenumodel-0.2.9+15.04.20150108/libqmenumodel/src/gtk/gtkmenutracker.c:257
  #15 0x in gtk_menu_tracker_model_changed (model=0x1185660 
[GDBusMenuModel], position=0, removed=1, added=0, user_data=0xade18b48)
  at 
/build/buildd/qmenumodel-0.2.9+15.04.20150108/libqmenumodel/src/gtk/gtkmenutracker.c:354
  #16 0x in ffi_call_VFP () at /usr/lib/arm-linux-gnueabihf/libffi.so.6
  ---Type  to continue, or q  to quit---
  #17 0x in ffi_call () at /usr/lib/arm-linux-gnueabihf/libffi.so.6
  #22 0x in  
(instance=, signal_id=, detail=0)
  at /build/buildd/glib2.0-2.44.0/./gobject/gsignal.c:3361
  #18 0x in g_cclosure_marshal_generic (closure=, 
return_gvalue=, n_param_values=4, param_values=, 
invocation_hint=0xbedfede8, marshal_data=0x0)
  at /build/buildd/glib2.0-2.44.0/./gobject/gclosure.c:1448
  #19 0x in g_closure_invoke (closure=0xed0ac0, return_value=0x0, 
n_param_values=4, param_values=0xbedfee30, invocation_hint=0xbedfede8)
  at /build/buildd/glib2.0-2.44.0/./gobject/gclosure.c:768
  #20 0x in signal_emit_unlocked_R (node=node@entry=0x85f3b8, 
detail=detail@entry=0, instance=0x1185660,
  instance@entry=0xb6226000, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0xbedfee30)
  at /build/buildd/glib2.0-2.44.0/./gobject/gsignal.c:3549
  #21 0x in g_signal_emit_valist (instance=, 
signal_id=, detail=detail@entry=3202346924, var_args=...,
  var_args@entry=...)
  at /build/buildd/glib2.0-2.44.0/./gobject/gsignal.c:3305
  

[Touch-packages] [Bug 1444170] Re: python code does not pass the flake8 static checks

[Leo Arias]

** Changed in: ubuntu-keyboard
   Status: New => In Progress

** Changed in: ubuntu-keyboard
 Assignee: (unassigned) => Leo Arias (elopio)

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

Title:
  python code does not pass the flake8 static checks

Status in Camera App:
  In Progress
Status in qakit - tools for the Canonical UEQA team:
  New
Status in Ubuntu Keyboard:
  In Progress
Status in address-book-app package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Flake8 checks that the python code follows the right code style, and
  does some static checks for errors.

  This branch is not passing the static tests.

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

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

[Touch-packages] [Bug 1444170] Re: python code does not pass the flake8 static checks

[Leo Arias]

** Changed in: camera-app
 Assignee: (unassigned) => Leo Arias (elopio)

** Changed in: camera-app
   Status: New => In Progress

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

Title:
  python code does not pass the flake8 static checks

Status in Camera App:
  In Progress
Status in qakit - tools for the Canonical UEQA team:
  New
Status in Ubuntu Keyboard:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Flake8 checks that the python code follows the right code style, and
  does some static checks for errors.

  This branch is not passing the static tests.

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

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

[Touch-packages] [Bug 1444170] Re: python code does not pass the flake8 static checks

[Leo Arias]

** Also affects: camera-app
   Importance: Undecided
   Status: New

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

Title:
  python code does not pass the flake8 static checks

Status in Camera App:
  New
Status in qakit - tools for the Canonical UEQA team:
  New
Status in Ubuntu Keyboard:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Flake8 checks that the python code follows the right code style, and
  does some static checks for errors.

  This branch is not passing the static tests.

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

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

[Touch-packages] [Bug 1444170] Re: python code does not pass the flake8 static checks

[Leo Arias]

** Also affects: ubuntu-keyboard
   Importance: Undecided
   Status: New

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

Title:
  python code does not pass the flake8 static checks

Status in qakit - tools for the Canonical UEQA team:
  New
Status in Ubuntu Keyboard:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Flake8 checks that the python code follows the right code style, and
  does some static checks for errors.

  This branch is not passing the static tests.

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

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

[Touch-packages] [Bug 1447206] Re: in autopilot tests, UnityTestCase setup is too big and complicated

[Leo Arias]

** Branch linked: lp:~canonical-platform-
qa/unity8/fix1447206-fixture_setup-1

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

Title:
  in autopilot tests, UnityTestCase setup is too big and complicated

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  The UnityTestCase setup in autopilot tests does a lot of things to
  prepare the environment and it has some conditionals to change the
  behaviour depending on the tests being run.

  This makes the setup too complicated and hard to reuse in other tests.
  If we inherit from that test case, we inherit the setup, so this it's
  not a good base to start new tests.

  An alternative is to write the setup as multiple fixtures, one per
  each environment detail we need. Fixtures allow to extend test cases
  by composition, so you choose the parts you want in each test, making
  the environment clearer.

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

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

[Touch-packages] [Bug 1306340] Re: In autopilot tests, the word Emulator is confusing

[Leo Arias]

** Summary changed:

- Rename CustomEmulatorBase to CustomProxyObjectBase
+ In autopilot tests, the word Emulator is confusing

** Description changed:

  As we are trying to remove the word Emulator from our vocabulary related
- to autopilot introspection, we should rename the CustomEmulatorBase,
- adding a deprecation message when somebody calls it by the old name.
+ to autopilot introspection because it can be confused with the project
+ used to emulate an android phone in a PC. We are replacing it with the
+ more accurate "Custom Proxy Object".
+ 
+ In autopilot:
+ - we should rename the CustomEmulatorBase, adding a deprecation message when 
somebody calls it by the old name.
+ - we should rename the emulator_base argument, adding a deprecation message 
too.

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Leo Arias (elopio)

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

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

Title:
  In autopilot tests, the word Emulator is confusing

Status in Autopilot:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  As we are trying to remove the word Emulator from our vocabulary
  related to autopilot introspection because it can be confused with the
  project used to emulate an android phone in a PC. We are replacing it
  with the more accurate "Custom Proxy Object".

  In autopilot:
  - we should rename the CustomEmulatorBase, adding a deprecation message when 
somebody calls it by the old name.
  - we should rename the emulator_base argument, adding a deprecation message 
too.

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

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

[Touch-packages] [Bug 1446499] Re: Updating scope from store removes it from favorites

[Leo Arias]

How can we prevent this from regressing?
Would it be enough to write unit tests for the new code with the fix, or should 
we write a higher level test that installs a scope, favorites it and then 
updates it?

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

Title:
  Updating scope from store removes it from favorites

Status in the base for Ubuntu mobile products:
  New
Status in Today Scope:
  Invalid
Status in unity-scope-click package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Using retail bq e4.5
  Saw an update for Today scope in the store today, so updated.
  After the Today scope was updated, I can no longer see the Today scope on my 
phone. 

  * No today scope running
  * No today scope listed from bottom edge.

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

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

[Touch-packages] [Bug 1447206] Re: in autopilot tests, UnityTestCase setup is too big and complicated

[Leo Arias]

Currently the fake sensors setup is implemented as one big fixture.
This duplicates some of the code in the base test case setup. We should extract 
some parts of the fake sensors setup into a base fixture, and use it in the 
base class.

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

Title:
  in autopilot tests, UnityTestCase setup is too big and complicated

Status in unity8 package in Ubuntu:
  New

Bug description:
  The UnityTestCase setup in autopilot tests does a lot of things to
  prepare the environment and it has some conditionals to change the
  behaviour depending on the tests being run.

  This makes the setup too complicated and hard to reuse in other tests.
  If we inherit from that test case, we inherit the setup, so this it's
  not a good base to start new tests.

  An alternative is to write the setup as multiple fixtures, one per
  each environment detail we need. Fixtures allow to extend test cases
  by composition, so you choose the parts you want in each test, making
  the environment clearer.

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

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

[Touch-packages] [Bug 1447206] [NEW] in autopilot tests, UnityTestCase setup is too big and complicated

[Leo Arias]

Public bug reported:

The UnityTestCase setup in autopilot tests does a lot of things to
prepare the environment and it has some conditionals to change the
behaviour depending on the tests being run.

This makes the setup too complicated and hard to reuse in other tests.
If we inherit from that test case, we inherit the setup, so this it's
not a good base to start new tests.

An alternative is to write the setup as multiple fixtures, one per each
environment detail we need. Fixtures allow to extend test cases by
composition, so you choose the parts you want in each test, making the
environment clearer.

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

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

Title:
  in autopilot tests, UnityTestCase setup is too big and complicated

Status in unity8 package in Ubuntu:
  New

Bug description:
  The UnityTestCase setup in autopilot tests does a lot of things to
  prepare the environment and it has some conditionals to change the
  behaviour depending on the tests being run.

  This makes the setup too complicated and hard to reuse in other tests.
  If we inherit from that test case, we inherit the setup, so this it's
  not a good base to start new tests.

  An alternative is to write the setup as multiple fixtures, one per
  each environment detail we need. Fixtures allow to extend test cases
  by composition, so you choose the parts you want in each test, making
  the environment clearer.

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

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

[Touch-packages] [Bug 1444170] Re: python code does not pass the flake8 static checks

[Leo Arias]

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

** Branch linked: lp:~canonical-platform-qa/qakit/flake8-fixes

** Changed in: qakit
 Assignee: (unassigned) => Federico Gimenez (fgimenez)

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

Title:
  python code does not pass the flake8 static checks

Status in qakit - tools for the Canonical UEQA team:
  New
Status in address-book-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Flake8 checks that the python code follows the right code style, and
  does some static checks for errors.

  This branch is not passing the static tests.

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

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

[Touch-packages] [Bug 1444170] Re: python code does not pass the flake8 static checks

[Leo Arias]

Hey osomon.

The problem on that script is that it's using the py2 version of flake8.
You need to run it like this:

python3 -m flake8 

I'll add that to my branch. Please check it, because I'm not sure if on
cmake I should be calling python3 directly; I have seen some fancier
things in some other projects.

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

Title:
  python code does not pass the flake8 static checks

Status in address-book-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Flake8 checks that the python code follows the right code style, and
  does some static checks for errors.

  This branch is not passing the static tests.

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

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

[Touch-packages] [Bug 1444170] Re: python code does not pass the flake8 static checks

[Leo Arias]

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

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

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Leo Arias (elopio)

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

Title:
  python code does not pass the flake8 static checks

Status in address-book-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Flake8 checks that the python code follows the right code style, and
  does some static checks for errors.

  This branch is not passing the static tests.

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

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

[Touch-packages] [Bug 1444170] [NEW] python code does not pass the flake8 static checks

[Leo Arias]

Public bug reported:

Flake8 checks that the python code follows the right code style, and
does some static checks for errors.

This branch is not passing the static tests.

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

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

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

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

Title:
  python code does not pass the flake8 static checks

Status in address-book-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Flake8 checks that the python code follows the right code style, and
  does some static checks for errors.

  This branch is not passing the static tests.

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

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

[Touch-packages] [Bug 1339191] Re: ubuntu-ui-toolkit-autopilot should not depend on py2

[Leo Arias]

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

** This bug has been marked a duplicate of bug 1429163
   Autopilot tests are compatible with py2

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

Title:
  ubuntu-ui-toolkit-autopilot should not depend on py2

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  ubuntu-ui-toolkit-autopilot should be installable in a python3 only
  manner, and not require or pull python2 depends, like python-
  autopilot, etc.

  We may need to create a   python3-ubuntu-ui-toolkit-autopilot and
  change the packages to use python3-ubuntu-ui-toolkit-autopilot, or
  python-ubuntu-ui-toolkit-autopilot for python2.

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

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

[Touch-packages] [Bug 1429163] Re: Autopilot tests are compatible with py2

[Leo Arias]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Leo Arias (elopio)

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

Title:
  Autopilot tests are compatible with py2

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The autopilot suite of tests and helpers in the toolkit is compatible
  with py2.

  We should drop the py2 support to simplify the code and to avoid all
  the py2 requirements that get installed when we want to run any test.

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

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

[Touch-packages] [Bug 1443663] [NEW] Add an autopilot helper to click a component

[Leo Arias]

Public bug reported:

In many places we are calling:

self.pointing_device.click_object(self.select_single(...))

Instead of that, it would be clearer to call:

self.select_single(...).click()

In that click helper, we should also check if the item is enabled and
visible. If not, an exception should be raised.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Add an autopilot helper to click a component

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  In many places we are calling:

  self.pointing_device.click_object(self.select_single(...))

  Instead of that, it would be clearer to call:

  self.select_single(...).click()

  In that click helper, we should also check if the item is enabled and
  visible. If not, an exception should be raised.

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

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

[Touch-packages] [Bug 1442851] Re: settings are too big for phone screen in portrait orientation

[Leo Arias]

** Summary changed:

- settings are two big for phone screen in portrait orientation
+ settings are too big for phone screen in portrait orientation

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

Title:
  settings are too big for phone screen in portrait orientation

Status in Ubuntu UX bugs:
  New
Status in Web Browser App:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  As shown on the attached screenshot, the rows #2 and #3 of the settings 
screen have a text that doesn't fit on the screen.
  The only way to see what these options mean is to switch the phone to 
landscape orientation.

  A different UI component should be used for these two options, one
  that allows the user to see the full text of what he's enabling or
  disabling.

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

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

[Touch-packages] [Bug 1442851] Re: settings are two big for phone screen in portrait orientation

[Leo Arias]

bug #1356640 was reported for the same issue, in system settings.

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

Title:
  settings are two big for phone screen in portrait orientation

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  As shown on the attached screenshot, the rows #2 and #3 of the settings 
screen have a text that doesn't fit on the screen.
  The only way to see what these options mean is to switch the phone to 
landscape orientation.

  A different UI component should be used for these two options, one
  that allows the user to see the full text of what he's enabling or
  disabling.

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

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

[Touch-packages] [Bug 1442851] [NEW] settings are two big for phone screen in portrait orientation

[Leo Arias]

Public bug reported:

As shown on the attached screenshot, the rows #2 and #3 of the settings screen 
have a text that doesn't fit on the screen.
The only way to see what these options mean is to switch the phone to landscape 
orientation.

A different UI component should be used for these two options, one that
allows the user to see the full text of what he's enabling or disabling.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "image20150411_053128472.jpg"
   
https://bugs.launchpad.net/bugs/1442851/+attachment/4372125/+files/image20150411_053128472.jpg

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

Title:
  settings are two big for phone screen in portrait orientation

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  As shown on the attached screenshot, the rows #2 and #3 of the settings 
screen have a text that doesn't fit on the screen.
  The only way to see what these options mean is to switch the phone to 
landscape orientation.

  A different UI component should be used for these two options, one
  that allows the user to see the full text of what he's enabling or
  disabling.

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

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

[Touch-packages] [Bug 1441893] Re: Can't connect to my wi-fi N network on vivid: authentication timed out

[Leo Arias]

sorry, scratch that last comment. It should have been:

I could connect to the N network on utopic, so this is a regression.

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

Title:
  Can't connect to my wi-fi N network on vivid: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: Ethernet Connection I217-V
     vendor: Intel Corporation
     physical id: 19
     bus info: pci@:00:19.0
     logical name: eth0
     version: 05
     serial: 00:90:f5:f8:ef:86
     size: 1Gbit/s
     capacity: 1Gbit/s
     width: 32 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
     resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
    *-network
     description: Wireless interface
     product: Wireless 3160
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:03:00.0
     logical name: wlan0
     version: 83
     serial: a0:88:69:39:ae:d6
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
     resources: irq:32 memory:f7c0-f7c01fff

  Attached is the full syslog.
  This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
  Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.

  I'm connecting to the same network using the same password with my
  other machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static  metric 1024
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   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-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2
   wlan0   wifi  disconnected  /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/1441893/+subscriptions

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

[Touch-packages] [Bug 1441893] Re: Can't connect to my wi-fi N network on vivid: authentication timed out

[Leo Arias]

I could connect to the G network on utopic, so this is a regression.

** Summary changed:

- Can't connect to my wi-fi N network: authentication timed out
+ Can't connect to my wi-fi N network on vivid: authentication timed out

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

Title:
  Can't connect to my wi-fi N network on vivid: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: Ethernet Connection I217-V
     vendor: Intel Corporation
     physical id: 19
     bus info: pci@:00:19.0
     logical name: eth0
     version: 05
     serial: 00:90:f5:f8:ef:86
     size: 1Gbit/s
     capacity: 1Gbit/s
     width: 32 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
     resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
    *-network
     description: Wireless interface
     product: Wireless 3160
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:03:00.0
     logical name: wlan0
     version: 83
     serial: a0:88:69:39:ae:d6
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
     resources: irq:32 memory:f7c0-f7c01fff

  Attached is the full syslog.
  This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
  Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.

  I'm connecting to the same network using the same password with my
  other machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static  metric 1024
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   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-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2
   wlan0   wifi  disconnected  /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/1441893/+subscriptions

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

[Touch-packages] [Bug 1441893] Re: Can't connect to my wi-fi N network: authentication timed out

[Leo Arias]

I switched the network back to G, and I can connect.

** Summary changed:

- Can't connect to my wi-fi: authentication timed out
+ Can't connect to my wi-fi N network: authentication timed out

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

Title:
  Can't connect to my wi-fi N network: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: Ethernet Connection I217-V
     vendor: Intel Corporation
     physical id: 19
     bus info: pci@:00:19.0
     logical name: eth0
     version: 05
     serial: 00:90:f5:f8:ef:86
     size: 1Gbit/s
     capacity: 1Gbit/s
     width: 32 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
     resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
    *-network
     description: Wireless interface
     product: Wireless 3160
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:03:00.0
     logical name: wlan0
     version: 83
     serial: a0:88:69:39:ae:d6
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
     resources: irq:32 memory:f7c0-f7c01fff

  Attached is the full syslog.
  This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
  Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.

  I'm connecting to the same network using the same password with my
  other machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static  metric 1024
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   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-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2
   wlan0   wifi  disconnected  /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/1441893/+subscriptions

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

[Touch-packages] [Bug 1441893] Re: Can't connect to my wi-fi: authentication timed out

[Leo Arias]

** Description changed:

  I can't connect to my wi-fi with my laptop.
  
  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out
  
  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
-   *-network   
-description: Ethernet interface
-product: Ethernet Connection I217-V
-vendor: Intel Corporation
-physical id: 19
-bus info: pci@:00:19.0
-logical name: eth0
-version: 05
-serial: 00:90:f5:f8:ef:86
-size: 1Gbit/s
-capacity: 1Gbit/s
-width: 32 bits
-clock: 33MHz
-capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
-configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
-resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
-   *-network
-description: Wireless interface
-product: Wireless 3160
-vendor: Intel Corporation
-physical id: 0
-bus info: pci@:03:00.0
-logical name: wlan0
-version: 83
-serial: a0:88:69:39:ae:d6
-width: 64 bits
-clock: 33MHz
-capabilities: bus_master cap_list ethernet physical wireless
-configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
-resources: irq:32 memory:f7c0-f7c01fff
+   *-network
+    description: Ethernet interface
+    product: Ethernet Connection I217-V
+    vendor: Intel Corporation
+    physical id: 19
+    bus info: pci@:00:19.0
+    logical name: eth0
+    version: 05
+    serial: 00:90:f5:f8:ef:86
+    size: 1Gbit/s
+    capacity: 1Gbit/s
+    width: 32 bits
+    clock: 33MHz
+    capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
+    configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
+    resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
+   *-network
+    description: Wireless interface
+    product: Wireless 3160
+    vendor: Intel Corporation
+    physical id: 0
+    bus info: pci@:03:00.0
+    logical name: wlan0
+    version: 83
+    serial: a0:88:69:39:ae:d6
+    width: 64 bits
+    clock: 33MHz
+    capabilities: bus_master cap_list ethernet physical wireless
+    configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
+    resources: irq:32 memory:f7c0-f7c01fff
  
  Attached is the full syslog.
- This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working. 
- Recently I changed the network from N to G, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
+ This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
+ Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.
  
  I'm connecting to the same network using the same password with my other
  machine.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  IpRoute:
-  default via 192.168.2.1 dev eth0  proto static  metric 1024 
-  169.254.0.0/16 dev eth0  scope link  metric 1000 
-  192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
+  default via 192.168.2.1 dev eth0  proto static  metric 1024
+  169.254.0.0/16 dev eth0  scope link  metric 1000
+  192.168

[Touch-packages] [Bug 1441893] [NEW] Can't connect to my wi-fi: authentication timed out

[Leo Arias]

Public bug reported:

I can't connect to my wi-fi with my laptop.

I get this error message in the syslog.
Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

ubuntu@ubuntu:~$ lshw -c network
WARNING: you should run this program as super-user.
  *-network   
   description: Ethernet interface
   product: Ethernet Connection I217-V
   vendor: Intel Corporation
   physical id: 19
   bus info: pci@:00:19.0
   logical name: eth0
   version: 05
   serial: 00:90:f5:f8:ef:86
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
   resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
  *-network
   description: Wireless interface
   product: Wireless 3160
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:03:00.0
   logical name: wlan0
   version: 83
   serial: a0:88:69:39:ae:d6
   width: 64 bits
   clock: 33MHz
   capabilities: bus_master cap_list ethernet physical wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
   resources: irq:32 memory:f7c0-f7c01fff

Attached is the full syslog.
This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working. 
Recently I changed the network from N to G, and recently did an upgrade to the 
latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
I've just tested with a daily vivid live USB, and the same problem happened.

I'm connecting to the same network using the same password with my other
machine.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu11
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CasperVersion: 1.356
CurrentDesktop: Unity
Date: Wed Apr  8 22:20:03 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.2.1 dev eth0  proto static  metric 1024 
 169.254.0.0/16 dev eth0  scope link  metric 1000 
 192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=xterm
 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-dev:
 DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 wlan0   wifi  disconnected  /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'.

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


** Tags: amd64 apport-bug vivid

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1441893/+attachment/4369887/+files/syslog

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

Title:
  Can't connect to my wi-fi: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
*-network   
 description: Ethernet interface
 product: Ethernet Connec

[Touch-packages] [Bug 1434518] Re: test_can_unlock_pin_screen broken under py3

[Leo Arias]

** Changed in: unity8 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  test_can_unlock_pin_screen broken under py3

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Revision 1680¹ wrongly removed the py3 compatibility bit, resulting in
  a failure in tablet scenario:

  Traceback (most recent call last):
File 
"/home/michal/dev/canonical/unity8/repo/tests/autopilot/unity8/shell/tests/test_lock_screen.py",
 line 47, in test_can_unlock_pin_screen
  self._enter_prompt_passphrase("1234\n")
File 
"/home/michal/dev/canonical/unity8/repo/tests/autopilot/unity8/shell/tests/test_lock_screen.py",
 line 138, in _enter_prompt_passphrase
  if not isinstance(passphrase, basestring):
  NameError: name 'basestring' is not defined

  ¹ http://bazaar.launchpad.net/~unity-
  
team/unity8/trunk/revision/1680#tests/autopilot/unity8/shell/tests/test_lock_screen.py

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 20 12:19:15 2015
  SourcePackage: unity8
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1432930] Re: move out of range printed when dragging a list view item

[Leo Arias]

zsombi explained that the onDragUpdated in the attached qml was wrong.
Changing it to:
if (event.status == ListItemDrag.Moving) {
   model.move(event.from, event.to, 1)
}

makes it work without errors. Marking the bug as invalid.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

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

Title:
  move out of range printed when dragging a list view item

Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  To reproduce:
  Open the attached qml file with qmlscene.
  Long click on the first item of the list. The drag handlers will appear.
  Click the drag handler.

  This will be printed on the console:
  
file:///home/elopio/workspace/canonical/ubuntu-ui-toolkit/experimental/autopilot-listview/tests/autopilot/ubuntuuitoolkit/tests/custom_proxy_objects/test_listitem.ListViewDraggingTestCase.qml:38:20:
 QML ListModel: move: out of range

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

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

[Touch-packages] [Bug 1318144] Re: Can't edit reviews

[Leo Arias]

Alecu, I think this story needs an user acceptance test:

Install a click package [1]
Open the store scope
Search for the installed app.
Open the preview.
Select 3 stars.
Write a review: "test review"
Click send.
Select 4 stars.
Edit the review: "test review edited"
Click send.
Assert that the review was edited.

I think the other details of the story can be tested with lower level tests.
Let us know if you need a hand getting started with the high level test.

[1] This can be done behind the UI, like in https://bazaar.launchpad.net
/~canonical-platform-qa/ubuntu-sanity-
tests/trunk/view/head:/ubuntu_sanity_tests/helpers/click.py#L31

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

Title:
  Can't edit reviews

Status in Ratings and Reviews server:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  It seems impossible to edit reviews at the moment. I get the review
  entry even though I reviewed already and I'm allowed to send another
  review, which actually gets lost somewhere.

  I imagine we want to limit the number of reviews to 1 per U1 account,
  but it should be possible to send a new/modified one. Maybe the review
  entry should be pre-filled with the previous review so it's obvious
  you can edit?

To manage notifications about this bug go to:
https://bugs.launchpad.net/rnr-server/+bug/1318144/+subscriptions

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

[Touch-packages] [Bug 1432930] [NEW] move out of range printed when dragging a list view item

[Leo Arias]

Public bug reported:

To reproduce:
Open the attached qml file with qmlscene.
Long click on the first item of the list. The drag handlers will appear.
Click the drag handler.

This will be printed on the console:
file:///home/elopio/workspace/canonical/ubuntu-ui-toolkit/experimental/autopilot-listview/tests/autopilot/ubuntuuitoolkit/tests/custom_proxy_objects/test_listitem.ListViewDraggingTestCase.qml:38:20:
 QML ListModel: move: out of range

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "test_listitem.ListViewDraggingTestCase.qml"
   
https://bugs.launchpad.net/bugs/1432930/+attachment/4347547/+files/test_listitem.ListViewDraggingTestCase.qml

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

Title:
  move out of range printed when dragging a list view item

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  To reproduce:
  Open the attached qml file with qmlscene.
  Long click on the first item of the list. The drag handlers will appear.
  Click the drag handler.

  This will be printed on the console:
  
file:///home/elopio/workspace/canonical/ubuntu-ui-toolkit/experimental/autopilot-listview/tests/autopilot/ubuntuuitoolkit/tests/custom_proxy_objects/test_listitem.ListViewDraggingTestCase.qml:38:20:
 QML ListModel: move: out of range

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

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

[Touch-packages] [Bug 1368343] Re: [wizard] on the security page, there's a long delay until the keyboard appears

[Leo Arias]

Yes, it is still slow to appear. I tested in krillin vivid 141.

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

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

Title:
   [wizard] on the security page, there's a long delay until the
  keyboard appears

Status in Ubuntu Keyboard:
  Invalid
Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  On the security page of the wizard, if you select passphrase and click
  on the text field, the on-screen keyboard can take up to 5 seconds to
  appear.

  On krillin, it happens for me for any language. On mako, if I select
  english first then the keyboard appears immediately. If I select
  spanish, it's slow. If then I select english again, it's still slow.
  So if you have problems reproducing this, just set the spanish
  language.

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

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

[Touch-packages] [Bug 1429200] Re: some autopilot tests fail to dismiss the greeter

[Leo Arias]

It might be useful to note that Brendan and I have seen a weird greeter 
behavior after doing some unity restarts.
What we see is that the swipe from right to left doesn't work. The swipe from 
left to right dismisses the greeter and shows the security page, but the osk 
never appears.

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

Title:
  some autopilot tests fail to dismiss the greeter

Status in unity8 package in Ubuntu:
  New

Bug description:
  Some autopilot tests are failing with:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/unity8/shell/tests/test_lock_screen.py", line 
72, in test_pin_screen_wrong_code
  greeter.swipe()
File "/usr/lib/python3/dist-packages/unity8/shell/emulators/greeter.py", 
line 59, in swipe
  self.wait_swiped_away()
File "/usr/lib/python3/dist-packages/unity8/shell/emulators/greeter.py", 
line 43, in wait_swiped_away
  raise AssertionError("Greeter cover page still up after 10s")
  AssertionError: Greeter cover page still up after 10s

  The screenshot shows that the greeter is still visible. The test log
  shows that the finger events were fired.

  For example:
  
https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/1492/testReport/junit/unity8.shell.tests.test_lock_screen/TestLockscreen/test_can_unlock_pin_screen_Native_Device_/

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

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

[Touch-packages] [Bug 1429200] [NEW] some autopilot tests fail to dismiss the greeter

[Leo Arias]

Public bug reported:

Some autopilot tests are failing with:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unity8/shell/tests/test_lock_screen.py", 
line 72, in test_pin_screen_wrong_code
greeter.swipe()
  File "/usr/lib/python3/dist-packages/unity8/shell/emulators/greeter.py", line 
59, in swipe
self.wait_swiped_away()
  File "/usr/lib/python3/dist-packages/unity8/shell/emulators/greeter.py", line 
43, in wait_swiped_away
raise AssertionError("Greeter cover page still up after 10s")
AssertionError: Greeter cover page still up after 10s

The screenshot shows that the greeter is still visible. The test log
shows that the finger events were fired.

For example:
https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/1492/testReport/junit/unity8.shell.tests.test_lock_screen/TestLockscreen/test_can_unlock_pin_screen_Native_Device_/

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

** Attachment added: "unity8.log"
   https://bugs.launchpad.net/bugs/1429200/+attachment/4336313/+files/unity8.log

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

Title:
  some autopilot tests fail to dismiss the greeter

Status in unity8 package in Ubuntu:
  New

Bug description:
  Some autopilot tests are failing with:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/unity8/shell/tests/test_lock_screen.py", line 
72, in test_pin_screen_wrong_code
  greeter.swipe()
File "/usr/lib/python3/dist-packages/unity8/shell/emulators/greeter.py", 
line 59, in swipe
  self.wait_swiped_away()
File "/usr/lib/python3/dist-packages/unity8/shell/emulators/greeter.py", 
line 43, in wait_swiped_away
  raise AssertionError("Greeter cover page still up after 10s")
  AssertionError: Greeter cover page still up after 10s

  The screenshot shows that the greeter is still visible. The test log
  shows that the finger events were fired.

  For example:
  
https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/1492/testReport/junit/unity8.shell.tests.test_lock_screen/TestLockscreen/test_can_unlock_pin_screen_Native_Device_/

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

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

[Touch-packages] [Bug 1341681] Re: Autopilot tests should stop using deprecated emulators module

[Leo Arias]

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Leo Arias (elopio)

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

Title:
  Autopilot tests should stop using deprecated emulators module

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Dropping Letters:
  New
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  New
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  Fix Released
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Document Viewer application for Ubuntu devices:
  New
Status in File Manager application for Ubuntu devices:
  Fix Released
Status in RSS Feed Reader application for Ubuntu devices:
  Incomplete
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  Incomplete
Status in dialer-app package in Ubuntu:
  Fix Released
Status in reminders-app package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Autopilot tests should stop using deprecated emulators module. Instead
  the new custom_proxy_objects modules should be used and called
  directly.

  Please note until https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1341679 is fixed, the deprecation warning will still
  appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1341681/+subscriptions

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

[Touch-packages] [Bug 1429163] Re: Autopilot tests are compatible with py2

[Leo Arias]

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Leo Arias (elopio)

** Branch linked: lp:~canonical-platform-qa/unity8/nopy2

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

Title:
  Autopilot tests are compatible with py2

Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  The autopilot suite of tests and helpers in the toolkit is compatible
  with py2.

  We should drop the py2 support to simplify the code and to avoid all
  the py2 requirements that get installed when we want to run any test.

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

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

[Touch-packages] [Bug 1429158] [NEW] Autopilot tests depend on qt4

[Leo Arias]

Public bug reported:

When installing the autopilot tests, they bring qt4 dependencies that
are unnecessary.

The package with the autopilot tests depends on libautopilot-qt, which
installs both autopilot-qt4 and autopilot-qt5.

We can remove that dependency and add autopilot-qt5 and qttestability-
autopilot instead.

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

** Affects: camera-app (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: cordova-ubuntu (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: mediaplayer-app (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: notes-app (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-html5-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntuone-credentials (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Leo Arias (elopio)
 Status: In Progress

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

Title:
  Autopilot tests depend on qt4

Status in address-book-app package in Ubuntu:
  New
Status in camera-app package in Ubuntu:
  New
Status in click-update-manager package in Ubuntu:
  New
Status in cordova-ubuntu package in Ubuntu:
  New
Status in gallery-app package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in mediaplayer-app package in Ubuntu:
  New
Status in notes-app package in Ubuntu:
  New
Status in ubuntu-html5-theme package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-webapps-qml package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  When installing the autopilot tests, they bring qt4 dependencies that
  are unnecessary.

  The package with the autopilot tests depends on libautopilot-qt, which
  installs both autopilot-qt4 and autopilot-qt5.

  We can remove that dependency and add autopilot-qt5 and qttestability-
  autopilot instead.

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

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

[Touch-packages] [Bug 1429163] [NEW] Autopilot tests are compatible with py2

[Leo Arias]

Public bug reported:

The autopilot suite of tests and helpers in the toolkit is compatible
with py2.

We should drop the py2 support to simplify the code and to avoid all the
py2 requirements that get installed when we want to run any test.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Autopilot tests are compatible with py2

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The autopilot suite of tests and helpers in the toolkit is compatible
  with py2.

  We should drop the py2 support to simplify the code and to avoid all
  the py2 requirements that get installed when we want to run any test.

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

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

[Touch-packages] [Bug 1429158] Re: Autopilot tests depend on qt4

[Leo Arias]

libautopilot-qt
Reverse Depends:
  qttestability-autopilot:i386
  qttestability-autopilot:i386
  libautopilot-qt:i386
  autopilot-qt5:i386
  autopilot-qt5:i386
  autopilot-qt4:i386
  autopilot-qt4:i386
  unity8-autopilot
  unity-webapps-qml-autopilot
  unity-scope-click-autopilot
  ubuntuone-credentials-autopilot
  ubuntu-system-settings-autopilot
  ubuntu-keyboard-autopilot
  ubuntu-html5-ui-toolkit-autopilot
  ubuntu-html5-container-autopilot
  reminders-app-autopilot
  qttestability-autopilot
  qttestability-autopilot
  python3-autopilot-tests
  python3-autopilot
  python3-autopilot
  python-autopilot-tests
  python-autopilot
  python-autopilot
  notes-app-autopilot
  mediaplayer-app-autopilot
  libautopilot-qt-autopilot
  indicator-network-autopilot
  gallery-app-autopilot
  friends-app-autopilot
  cordova-ubuntu-autopilot
  click-update-manager-autopilot
  camera-app-autopilot
  autopilot-touch-legacy
  autopilot-qt5
  autopilot-qt5
  autopilot-qt4
  autopilot-qt4
  address-book-app-autopilot

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

** Branch linked: lp:~canonical-platform-qa/unity8/remove-qt4dep

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

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

** Also affects: ubuntuone-credentials (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

** Also affects: click-update-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Leo Arias (elopio)

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

Title:
  Autopilot tests depend on qt4

Status in address-book-app package in Ubuntu:
  New
Status in camera-app package in Ubuntu:
  New
Status in click-update-manager package in Ubuntu:
  New
Status in cordova-ubuntu package in Ubuntu:
  New
Status in gallery-app package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in mediaplayer-app package in Ubuntu:
  New
Status in notes-app package in Ubuntu:
  New
Status in ubuntu-html5-theme package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-webapps-qml package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  When installing the autopilot tests, they bring qt4 dependencies that
  are unnecessary.

  The package with the autopilot tests depends on libautopilot-qt, which
  installs both autopilot-qt4 and autopilot-qt5.

  We can remove that dependency and add autopilot-qt5 and qttestability-
  autopilot instead.

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

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

[Touch-packages] [Bug 1428114] Re: Need OSK input device on phones

[Leo Arias]

I agree with zombie that unit tests are needed. Ideally, you would find
a nice way to fake the OSK and trigger the events it is supposed to
trigger.

About the autopilot tests, I think we have everything we need now. We
need to extend get_keyboard with:

if model == touch:
if maliit is not running with testability:
   restart malit with testability
return ubuntu_keyboard.emulators.keyboard.Keyboard()
else:
return input.Keyboard.create()

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

Title:
  Need OSK input device on phones

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Currently although it may look as though we have an OSK in Autopilot
  tests running on phones, keyboard input emits synthetic events. This
  makes testing of particular behavior involving pre-edit text
  impossible to test. We don't have unit tests for this either because
  maliit is very hard to spawn, so we essentially never run any of the
  tests for it.

  def get_keyboard():   

  
  """Return the keyboard device."""
  # TODO return the OSK if we are on the phone. --elopio - 2014-01-13
  return input.Keyboard.create()

  As per my understanding we should have an input device that talks to
  maliit using introspection (accessibility?), which is the way tests
  run in ubuntu-keyboard, but those aren't right now re-usable by other
  projects.

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

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

[Touch-packages] [Bug 1423050] [NEW] App preview buttons appear before they can be clicked

[Leo Arias]

Public bug reported:

When I open the preview of an installed application, it shows the
uninstall and close buttons. If I click them while the bottom loading
bar is still moving, they will do nothing.

To reproduce:
Do a long touch in an app, for example, file manager
As soon as the buttons appear, touch one of them.
If you are fast and your connection is slow, then you will click the button 
before the images are fully loaded, so the progress bar will still be moving.
And nothing will happen.

Tested on krillin, vivid, r114

I think there should be a clear indication that the buttons are disabled
while the preview is being loaded. Or maybe it doesn't matter that the
images are not loaded, the buttons should be clickable as soon as they
appear.

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

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

Title:
  App preview buttons appear before they can be clicked

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  When I open the preview of an installed application, it shows the
  uninstall and close buttons. If I click them while the bottom loading
  bar is still moving, they will do nothing.

  To reproduce:
  Do a long touch in an app, for example, file manager
  As soon as the buttons appear, touch one of them.
  If you are fast and your connection is slow, then you will click the button 
before the images are fully loaded, so the progress bar will still be moving.
  And nothing will happen.

  Tested on krillin, vivid, r114

  I think there should be a clear indication that the buttons are
  disabled while the preview is being loaded. Or maybe it doesn't matter
  that the images are not loaded, the buttons should be clickable as
  soon as they appear.

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

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

[Touch-packages] [Bug 1422904] Re: Autopilot returns the wrong custom proxy object when a previous one was registered with the same name

[Leo Arias]

As a workaround, one of the classes can be renamed. But we need a better
solution for this. Maybe allowing a list of classes, instead of a single
item as the dictionary value.

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

Title:
  Autopilot returns the wrong custom proxy object when a previous one
  was registered with the same name

Status in autopilot package in Ubuntu:
  New

Bug description:
  We are hitting this issue on the sanity test, where we have two
  different custom proxy objects named LanguagePage. One is from system
  settings and the other is from unity.

  So the object registry will have:

  'LanguagePage': 

  When we try to select the language page from unity, it is nowhere on
  the registry so it will return a generic custom proxy object, instead
  of the custom one.

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

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

[Touch-packages] [Bug 1422904] [NEW] Autopilot returns the wrong custom proxy object when a previous one was registered with the same name

[Leo Arias]

Public bug reported:

We are hitting this issue on the sanity test, where we have two
different custom proxy objects named LanguagePage. One is from system
settings and the other is from unity.

So the object registry will have:

'LanguagePage': 

When we try to select the language page from unity, it is nowhere on the
registry so it will return a generic custom proxy object, instead of the
custom one.

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

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

Title:
  Autopilot returns the wrong custom proxy object when a previous one
  was registered with the same name

Status in autopilot package in Ubuntu:
  New

Bug description:
  We are hitting this issue on the sanity test, where we have two
  different custom proxy objects named LanguagePage. One is from system
  settings and the other is from unity.

  So the object registry will have:

  'LanguagePage': 

  When we try to select the language page from unity, it is nowhere on
  the registry so it will return a generic custom proxy object, instead
  of the custom one.

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

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

[Touch-packages] [Bug 1417118] Re: test_looses_focus_when_reloading fails when run on desktop

[Leo Arias]

After some digging, it seems that creating the Touch device is causing
the weird behaviour.

To reproduce, do this in a terminal:

$ python3
Python 3.4.2 (default, Dec 27 2014, 23:37:21) 
[GCC 4.9.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from autopilot.input._uinput import Touch
>>> Touch.create()


In a different terminal, do:

elopio@tangamandapio76-desktop:~/workspace/canonical/webbrowser-
app/trunk$ ./src/app/webbrowser/webbrowser-app --new-session
http://www.ubuntu.com/download

Wait for the page to load. Click the url bar so the refresh button
appears. Now click the refresh button a little to the right from the
center, and you will see what osomon attached in his video.

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

Title:
  test_looses_focus_when_reloading fails when run on desktop

Status in Autopilot:
  New
Status in Web Browser App:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Recently, the otto tests started runnning successfully again for the
  webbrowser-app CI job (they had been broken for a long time).

  Now they all pass but one:

  
webbrowser_app.tests.test_addressbar_states.TestAddressBarStates.test_looses_focus_when_reloading

  I’m attaching the test result output as well as a video capture of
  what happens when the test is run.

  It appears that clicking the reload button in the address bar doesn’t
  activate the reload action, but instead shows the contextual menu as
  if the click had gone through to the TextField below.

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

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

[Touch-packages] [Bug 1415318] Re: Music app crashes with unsupported schema version with latest v0.105+15.04.20150127-0ubuntu1 on Vivid

[Leo Arias]

This needs a test, right?
How can we check that a new release of media scanner won't break the apps that 
depend on it?

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

Title:
  Music app crashes with unsupported schema version with latest
  v0.105+15.04.20150127-0ubuntu1 on Vivid

Status in Media Scanner v2:
  New
Status in Music application for Ubuntu devices:
  Triaged
Status in mediascanner2 package in Ubuntu:
  Fix Released

Bug description:
  The music app is crashing on the latest vivid images. The following
  error is seen on console prior to the crash in image #80 for mako and
  #79 for flo--both of which update mediascanner2 to version
  0.105+15.04.20150127-0ubuntu1.

  terminate called after throwing an instance of 'std::runtime_error'
what():  Tried to open a db with an unsupported schema version.

  Was the something not updated? It seems like the daemon is the same
  schema version (8), but the plugin does not support this version.

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

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

[Touch-packages] [Bug 1401517] Re: Autopilot helper to swipe on flickables will fail if the bottom edge is bigger

[Leo Arias]

** Branch linked: lp:~canonical-platform-qa/ubuntu-ui-
toolkit/fix1401517-overwrite_swipe_borders

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Leo Arias (elopio)

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

Title:
  Autopilot helper to swipe on flickables will fail if the bottom edge
  is bigger

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The autopilot helper to swipe from the bottom to show more items that
  are not visible on the flickable has a hardcoded value of 25 px to
  start the swipe from the button.

  This value is good enough for apps like messaging and clock, because their 
bottom edge mouse area is small.
  But for the dash it opens the page to manage scope instead of swiping. Apps 
like the dash need a bigger margin to start the swipe.

  We should make it an attribute of the flickable, so it can be
  overriden by the classes that extend it.

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

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

[Touch-packages] [Bug 1401517] [NEW] Autopilot helper to swipe on flickables will fail if the bottom edge is bigger

[Leo Arias]

Public bug reported:

The autopilot helper to swipe from the bottom to show more items that
are not visible on the flickable has a hardcoded value of 25 px to start
the swipe from the button.

This value is good enough for apps like messaging and clock, because their 
bottom edge mouse area is small.
But for the dash it opens the page to manage scope instead of swiping. Apps 
like the dash need a bigger margin to start the swipe.

We should make it an attribute of the flickable, so it can be overriden
by the classes that extend it.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Autopilot helper to swipe on flickables will fail if the bottom edge
  is bigger

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The autopilot helper to swipe from the bottom to show more items that
  are not visible on the flickable has a hardcoded value of 25 px to
  start the swipe from the button.

  This value is good enough for apps like messaging and clock, because their 
bottom edge mouse area is small.
  But for the dash it opens the page to manage scope instead of swiping. Apps 
like the dash need a bigger margin to start the swipe.

  We should make it an attribute of the flickable, so it can be
  overriden by the classes that extend it.

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

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

[Touch-packages] [Bug 1398933] [NEW] Autopilot tests fail because the unity dash is now a separate process

[Leo Arias]

Public bug reported:

With the unity dash split, the current scope click autopilot tests
started failing.

There is a new base test case in the unity8 project that will take care
of setting up and starting the dash, and making it available for use
during scope tests. The click scope tests need to be updated to use this
base test case.

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Assignee: Leo Arias (elopio)
 Status: In Progress

** Changed in: unity-scope-click (Ubuntu)
   Status: New => In Progress

** Changed in: unity-scope-click (Ubuntu)
 Assignee: (unassigned) => Leo Arias (elopio)

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

Title:
  Autopilot tests fail because the unity dash is now a separate process

Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  With the unity dash split, the current scope click autopilot tests
  started failing.

  There is a new base test case in the unity8 project that will take
  care of setting up and starting the dash, and making it available for
  use during scope tests. The click scope tests need to be updated to
  use this base test case.

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

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

[Touch-packages] [Bug 1395863] Re: player controls are not displayed in the sound indicator while music is playing

[Leo Arias]

I've just found this: https://bugs.launchpad.net/ubuntu/+source
/indicator-sound/+bug/1381069

** Changed in: indicator-sound (Ubuntu)
   Status: New => Invalid

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

Title:
  player controls are not displayed in the sound indicator while music
  is playing

Status in “indicator-sound” package in Ubuntu:
  Invalid

Bug description:
  I flashed 15.04 in my krillin, image #37. And when I play music, the
  sound indicator doesn't show the play/pause controls.

  Steps to reproduce:
  plug your phone to the computer with the usb cable.
  copy a song to the Music folder.
  open the music app.
  play the song.

  swipe down the sound indicator. It should display the controls to play
  and pause the song, but shows nothing.

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

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

[Touch-packages] [Bug 1395863] Re: player controls are not displayed in the sound indicator while music is playing

[Leo Arias]

** Attachment added: "playing.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1395863/+attachment/4266947/+files/playing.png

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

Title:
  player controls are not displayed in the sound indicator while music
  is playing

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  I flashed 15.04 in my krillin, image #37. And when I play music, the
  sound indicator doesn't show the play/pause controls.

  Steps to reproduce:
  plug your phone to the computer with the usb cable.
  copy a song to the Music folder.
  open the music app.
  play the song.

  swipe down the sound indicator. It should display the controls to play
  and pause the song, but shows nothing.

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

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

[Touch-packages] [Bug 1395863] [NEW] player controls are not displayed in the sound indicator while music is playing

[Leo Arias]

Public bug reported:

I flashed 15.04 in my krillin, image #37. And when I play music, the
sound indicator doesn't show the play/pause controls.

Steps to reproduce:
plug your phone to the computer with the usb cable.
copy a song to the Music folder.
open the music app.
play the song.

swipe down the sound indicator. It should display the controls to play
and pause the song, but shows nothing.

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

** Description changed:

  I flashed 15.04 in my krillin, image #37. And when I play music, the
  sound indicator doesn't show the play/pause controls.
  
  Steps to reproduce:
  plug your phone to the computer with the usb cable.
  copy a song to the Music folder.
  open the music app.
  play the song.
  
- swipe down the sound indicator. It should
+ swipe down the sound indicator. It should display the controls to play
+ and pause the song, but shows nothing.

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

Title:
  player controls are not displayed in the sound indicator while music
  is playing

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  I flashed 15.04 in my krillin, image #37. And when I play music, the
  sound indicator doesn't show the play/pause controls.

  Steps to reproduce:
  plug your phone to the computer with the usb cable.
  copy a song to the Music folder.
  open the music app.
  play the song.

  swipe down the sound indicator. It should display the controls to play
  and pause the song, but shows nothing.

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

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

[Touch-packages] [Bug 1393862] [NEW] README file is empty

[Leo Arias]

Public bug reported:

The readme file should include at least instructions to:

- build the project
- run the project
- run the tests

The current README file is empty, which makes it hard for new people to
collaborate with this project.

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

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

Title:
   README file is empty

Status in “indicator-messages” package in Ubuntu:
  New

Bug description:
  The readme file should include at least instructions to:

  - build the project
  - run the project
  - run the tests

  The current README file is empty, which makes it hard for new people
  to collaborate with this project.

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

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

[Touch-packages] [Bug 1382267] Re: edges intro fails on rtm krillin 112

[Leo Arias]

** Branch linked: lp:~unity-team/unity8/edgedemo-update-indicators

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

Title:
  edges intro fails on rtm krillin 112

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  On rtm krillin image 112, the edges intro doesn't work.  After swiping
  down from the top to reveal an indicator menu, the bottom-edge
  tutorial overlay doesn't appear.  However, if I swipe it up anyway,
  the final edge overlay appears and I can proceed to use the device.
  Only one of the five overlays fails (right, top, bottom, left, tap...
  bottom fails).

  This worked in image 109.

  Update: Saviq reports it's also failing on 109.

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

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

[Touch-packages] [Bug 1382283] Re: wifi toggle interrupts sound playback

[Leo Arias]

Confirmed on krillin #112. It doesn't happen on mako #93.

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

Title:
  wifi toggle interrupts sound playback

Status in “indicator-network” package in Ubuntu:
  Confirmed

Bug description:
  Not really sure where this bug should go, but on recent rtm krillin
  images (such as 112), turning wifi on/off in the network indicator
  causes a brief interruption in music playback.

  Steps to reproduce the issue:
  1. Start playing a song in the music app.
  2. Pull down the network indicator.
  3. Toggle wi-fi on or off.

  For some reason, this makes the sound pause for a moment.

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

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

[Touch-packages] [Bug 1318008] Re: Core apps .desktop files do not include translated strings

[Leo Arias]

Bug #1382317.

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

Title:
  Core apps .desktop files do not include translated strings

Status in Address Book App:
  Fix Released
Status in Camera App:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  Fix Released
Status in Dropping Letters:
  Invalid
Status in Gallery App:
  Fix Released
Status in Media Player App:
  Fix Released
Status in Messaging App:
  Fix Released
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  In Progress
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  Triaged
Status in Calculator application for Ubuntu devices:
  Fix Released
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Ubuntu Clock App reboot series:
  Fix Released
Status in File Manager application for Ubuntu devices:
  Fix Released
Status in RSS Feed Reader application for Ubuntu devices:
  Fix Released
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Ubuntu Translations:
  Triaged
Status in Weather application for Ubuntu devices:
  Fix Released
Status in Web Browser App:
  Fix Released
Status in “camera-app” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu:
  Fix Released
Status in “messaging-app” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  As other apps cannot know where .mo files might be located for click
  packages, and unity8 apparently does not know about X-Ubuntu-Gettext-
  Domain for deb packages, the .desktop files for any applications will
  need to have their translations merged back into the .desktop file
  itself. This at a minimum should include the following .desktop
  fields:

  Name
  Comment
  Keywords (semicolon-separated list of strings)

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1318008/+subscriptions

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

[Touch-packages] [Bug 1318008] Re: Core apps .desktop files do not include translated strings

[Leo Arias]

Media Player is still not translatable. I'm not sure why the fix by
renato is removing the string from the pot. I'll report a new bug for it
as I can't return the task in this one back to new.

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

Title:
  Core apps .desktop files do not include translated strings

Status in Address Book App:
  Fix Released
Status in Camera App:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  Fix Released
Status in Dropping Letters:
  Invalid
Status in Gallery App:
  Fix Released
Status in Media Player App:
  Fix Released
Status in Messaging App:
  Fix Released
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  In Progress
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  Triaged
Status in Calculator application for Ubuntu devices:
  Fix Released
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Ubuntu Clock App reboot series:
  Fix Released
Status in File Manager application for Ubuntu devices:
  Fix Released
Status in RSS Feed Reader application for Ubuntu devices:
  Fix Released
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Ubuntu Translations:
  Triaged
Status in Weather application for Ubuntu devices:
  Fix Released
Status in Web Browser App:
  Fix Released
Status in “camera-app” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu:
  Fix Released
Status in “messaging-app” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  As other apps cannot know where .mo files might be located for click
  packages, and unity8 apparently does not know about X-Ubuntu-Gettext-
  Domain for deb packages, the .desktop files for any applications will
  need to have their translations merged back into the .desktop file
  itself. This at a minimum should include the following .desktop
  fields:

  Name
  Comment
  Keywords (semicolon-separated list of strings)

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1318008/+subscriptions

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

[Touch-packages] [Bug 1368856] Re: [Indicators] Update indicators to match the latest design

[Leo Arias]

I can understand some of the reasons for that behaviour. But then can we
make something like keeping some indicators pined to the top bar? For
example, I use the gps a lot, but I don't want it enabled when I'm not
using it because it will consume my battery . I would like a quick way
to enable and disable GPS, without having to open the system settings.

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

Title:
  [Indicators] Update indicators to match the latest design

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  There is a new indicators design that improves and fixes many of the
  usability issues in the current design.

  New design fixes following issues:
  1. Too small target size for reliably making selection -> false positives
  2. Current design doesn’t support overflow. Or inactive items so that their 
menu could be accessed.
  3. Movement overload when item changes while going down.
  4. Tabs. Deprecated component and poor navigation.
  5. Invisible locking line in mid point of the screen.

  Specification can be found here:
  
https://docs.google.com/a/canonical.com/document/d/1jHIGzAzf7kFELgOiU9J0Hd9mOa3NzTsnEglLmx_qEfk/edit

  There is also a prototype of the new design:
  It can be found here: lp:~willow-team/willow/Indicators-Bens-idea/

  There is also a screencast video of the prototype in action here:
  
https://docs.google.com/a/canonical.com/file/d/0B8eY_FZZ1z7IN0ZaazhwOUhjdnc/edit

  Implementing this would be one way of fixing bug 1285951, bug 1352784,
  and bug 1370799.

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

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

[Touch-packages] [Bug 1379381] Re: [Dash] shows splash screen with "Scopes" when starting up the phone

[Leo Arias]

In addition to this, once the splash is gone we will have a white screen for 
around 5 seconds while the icons and the header are loaded. I'm not sure if 
that should be reported as a separate bug.
During the first boot, we are already seeing a spinning ubuntu wheel, so 
putting something like another loading image while the icons are loaded sound 
like a bad first experience.

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

Title:
  [Dash] shows splash screen with "Scopes" when starting up the phone

Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10 r274

  1. Start up the phone.
  2. Immediately when the welcome screen appears, unlock it.

  What you see: A splash screen with the word "Scopes".

  What you should see: The first thing you see on unlocking the phone
  should not be the word "Scopes".

  Some of the ways this bug could be fixed:
  - rename the Dash app from "Scopes" to "Ubuntu"
  - use a different splash screen mode for the Dash
  - special-case the Dash so that it has no splash screen at all

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

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

[Touch-packages] [Bug 1368856] Re: [Indicators] Update indicators to match the latest design

[Leo Arias]

I don't understand how the new design fixes bug #1285951.
What's the expected flow to re enable the bluetooth? Open system settings and 
go to the bluetooth section?

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

Title:
  [Indicators] Update indicators to match the latest design

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  There is a new indicators design that improves and fixes many of the
  usability issues in the current design.

  New design fixes following issues:
  1. Too small target size for reliably making selection -> false positives
  2. Current design doesn’t support overflow. Or inactive items so that their 
menu could be accessed.
  3. Movement overload when item changes while going down.
  4. Tabs. Deprecated component and poor navigation.
  5. Invisible locking line in mid point of the screen.

  Specification can be found here:
  
https://docs.google.com/a/canonical.com/document/d/1jHIGzAzf7kFELgOiU9J0Hd9mOa3NzTsnEglLmx_qEfk/edit

  There is also a prototype of the new design:
  It can be found here: lp:~willow-team/willow/Indicators-Bens-idea/

  There is also a screencast video of the prototype in action here:
  
https://docs.google.com/a/canonical.com/file/d/0B8eY_FZZ1z7IN0ZaazhwOUhjdnc/edit

  Implementing this would be one way of fixing bug 1285951, bug 1352784,
  and bug 1370799.

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

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

[Touch-packages] [Bug 1377939] Re: Scope using location cause a dialog "An unconfined application wants to access your current location"

[Leo Arias]

** Attachment added: "unconfined.png"
   
https://bugs.launchpad.net/unity-scope-onlinemusic/+bug/1377939/+attachment/4237807/+files/unconfined.png

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

Title:
  Scope using location cause a dialog "An unconfined application wants
  to access your current location"

Status in Ubuntu UX bugs:
  Triaged
Status in Unity Online Music Scope:
  New
Status in “location-service” package in Ubuntu:
  Confirmed

Bug description:
  Swiping to the flickr scope yields a confusing dialog.

  Build: 20141006
  Clean install (--wipe)

  What you expected to happen
  If flickr/a scope wants to access my location, I expected to be asked that

  What happened instead
  I was asked if an unconfined app could use my location.
  "unconfined
  An unconfined applications wants to access your current location
  [deny] [allow]"

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

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

[Touch-packages] [Bug 1377939] Re: Scope using location cause a dialog "An unconfined application wants to access your current location"

[Leo Arias]

Tested on krillin image #109 14.09-proposed. It also affects the music scope, 
that is one of the first things new users will find.
This should be high or critical because it affects the first boot experience.

** Also affects: unity-scope-onlinemusic
   Importance: Undecided
   Status: New

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

Title:
  Scope using location cause a dialog "An unconfined application wants
  to access your current location"

Status in Ubuntu UX bugs:
  Triaged
Status in Unity Online Music Scope:
  New
Status in “location-service” package in Ubuntu:
  Confirmed

Bug description:
  Swiping to the flickr scope yields a confusing dialog.

  Build: 20141006
  Clean install (--wipe)

  What you expected to happen
  If flickr/a scope wants to access my location, I expected to be asked that

  What happened instead
  I was asked if an unconfined app could use my location.
  "unconfined
  An unconfined applications wants to access your current location
  [deny] [allow]"

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

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

[Touch-packages] [Bug 1368343] Re: [wizard] on the security page, there's a long delay until the keyboard appears

[Leo Arias]

Got it.
Just a heads up that I added this bug to the readiness report send by Julien 
every week.

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

Title:
   [wizard] on the security page, there's a long delay until the
  keyboard appears

Status in Ubuntu Keyboard:
  Invalid
Status in “ubuntu-keyboard” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  Confirmed

Bug description:
  On the security page of the wizard, if you select passphrase and click
  on the text field, the on-screen keyboard can take up to 5 seconds to
  appear.

  On krillin, it happens for me for any language. On mako, if I select
  english first then the keyboard appears immediately. If I select
  spanish, it's slow. If then I select english again, it's still slow.
  So if you have problems reproducing this, just set the spanish
  language.

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

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

[Touch-packages] [Bug 1378920] [NEW] changing volume with mediaplayer playing pauses the video

[Leo Arias]

Public bug reported:

Dave found this while testing silo 11. I reproduced with krilling 14.09
proposed #91.

Steps to reproduce:
Put a video on the Videos folder of the phone.
Go to the video scope.
Open a video and play it.
While the video is playing, press the volume up or down buttons.

The video freezes. It seems paused, but the pause button is still
visible. If you click pause and play, then the video resumes.

phablet@ubuntu-phablet:~$ apt-cache policy indicator-sound
indicator-sound:
  Instalados: 12.10.2+14.10.20141007-0ubuntu1
  Candidato: 12.10.2+14.10.20141007-0ubuntu1
  Tabla de versión:
 *** 12.10.2+14.10.20141007-0ubuntu1 0
500 
http://ppa.launchpad.net/ci-train-ppa-service/landing-011/ubuntu-rtm/ 
14.09/main armhf Packages
100 /var/lib/dpkg/status

** Affects: indicator-sound
 Importance: Undecided
 Status: New

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

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

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

Title:
  changing volume with mediaplayer playing pauses the video

Status in Sound Menu:
  New
Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Dave found this while testing silo 11. I reproduced with krilling
  14.09 proposed #91.

  Steps to reproduce:
  Put a video on the Videos folder of the phone.
  Go to the video scope.
  Open a video and play it.
  While the video is playing, press the volume up or down buttons.

  The video freezes. It seems paused, but the pause button is still
  visible. If you click pause and play, then the video resumes.

  phablet@ubuntu-phablet:~$ apt-cache policy indicator-sound
  indicator-sound:
Instalados: 12.10.2+14.10.20141007-0ubuntu1
Candidato: 12.10.2+14.10.20141007-0ubuntu1
Tabla de versión:
   *** 12.10.2+14.10.20141007-0ubuntu1 0
  500 
http://ppa.launchpad.net/ci-train-ppa-service/landing-011/ubuntu-rtm/ 
14.09/main armhf Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1378920/+subscriptions

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

[Touch-packages] [Bug 1378618] [NEW] volume notification looks bad when an indicator is open

[Leo Arias]

Public bug reported:

I found this while testing silo 11 with krilling #88.

Steps to reproduce:
Open an indicator.
Press a volume button.

(see the attached screenshot)

You will see that the notification appears, but it's the same color as
the header. It has no borders, so you can't tell it's a popup. It looks
like the header changed to something that's no properly aligned.

phablet@ubuntu-phablet:~$ apt-cache policy indicator-sound
indicator-sound:
  Instalados: 12.10.2+14.10.20141007-0ubuntu1
  Candidato: 12.10.2+14.10.20141007-0ubuntu1
  Tabla de versión:
 *** 12.10.2+14.10.20141007-0ubuntu1 0
500 
http://ppa.launchpad.net/ci-train-ppa-service/landing-011/ubuntu-rtm/ 
14.09/main armhf Packages
100 /var/lib/dpkg/status

** Affects: indicator-sound
 Importance: Undecided
 Status: New

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

** Attachment added: "volume2.png"
   
https://bugs.launchpad.net/bugs/1378618/+attachment/4227991/+files/volume2.png

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

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  volume notification looks bad when an indicator is open

Status in Sound Menu:
  New
Status in Ubuntu UX bugs:
  New
Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  I found this while testing silo 11 with krilling #88.

  Steps to reproduce:
  Open an indicator.
  Press a volume button.

  (see the attached screenshot)

  You will see that the notification appears, but it's the same color as
  the header. It has no borders, so you can't tell it's a popup. It
  looks like the header changed to something that's no properly aligned.

  phablet@ubuntu-phablet:~$ apt-cache policy indicator-sound
  indicator-sound:
Instalados: 12.10.2+14.10.20141007-0ubuntu1
Candidato: 12.10.2+14.10.20141007-0ubuntu1
Tabla de versión:
   *** 12.10.2+14.10.20141007-0ubuntu1 0
  500 
http://ppa.launchpad.net/ci-train-ppa-service/landing-011/ubuntu-rtm/ 
14.09/main armhf Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1378618/+subscriptions

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

[Touch-packages] [Bug 1378616] Re: changing volume with the indicator open makes the slider shiver and the mediaplayer icon to be reloaded and the pause button to appear

[Leo Arias]

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

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

Title:
  changing volume with the indicator open makes the slider shiver and
  the mediaplayer icon to be reloaded and the pause button to appear

Status in Sound Menu:
  New
Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  I found this while testing silo 11 with krilling #88.

  Steps to reproduce:
  Open the sound indicator.
  Press a volume button.

  (see the attached video)

  You will see that the slider moves to the right value, then moves to a 
different place, and then returns to the right value.
  Also the mediaplayer icon disappears for a while.
  And the play button changes to the pause button for a while.

  phablet@ubuntu-phablet:~$ apt-cache policy indicator-sound
  indicator-sound:
Instalados: 12.10.2+14.10.20141007-0ubuntu1
Candidato: 12.10.2+14.10.20141007-0ubuntu1
Tabla de versión:
   *** 12.10.2+14.10.20141007-0ubuntu1 0
  500 
http://ppa.launchpad.net/ci-train-ppa-service/landing-011/ubuntu-rtm/ 
14.09/main armhf Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1378616/+subscriptions

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

[Touch-packages] [Bug 1368343] Re: [wizard] on the security page, there's a long delay until the keyboard appears

[Leo Arias]

>From what Michael Sheldon said, I would just like to say that there is
also a long delay without changing the language.

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

Title:
   [wizard] on the security page, there's a long delay until the
  keyboard appears

Status in Ubuntu Keyboard:
  Invalid
Status in “ubuntu-keyboard” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  Confirmed

Bug description:
  On the security page of the wizard, if you select passphrase and click
  on the text field, the on-screen keyboard can take up to 5 seconds to
  appear.

  On krillin, it happens for me for any language. On mako, if I select
  english first then the keyboard appears immediately. If I select
  spanish, it's slow. If then I select english again, it's still slow.
  So if you have problems reproducing this, just set the spanish
  language.

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

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