[Touch-packages] [Bug 1452751] Re: Connecting network jump is confusing

2021-01-27 Thread Matthew Paul Thomas
** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: Matthew Paul Thomas (mpt) => (unassigned)

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

Title:
  Connecting network jump is confusing

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 r23

  1. Do any of the following:
  - open System Settings > "Wi-Fi"
  - open the network indicator
  - flash the phone and go to the "Connect to Wi-Fi" step

  2. Tap a closed network that is not on top and that you haven't used
  before

  Behaviour I get:
  Network jumps to top. After a while a prompt pops up to request your 
password. This can take up to 5 second on slow networks.
  This is very confusing. When the network jumped to the top, I wasn't sure if 
I tapped it, so I tapped it again. This had the following result: *popup asking 
for password appears* *popup goes away almost immediately* *popup comes back 
after a few seconds*

  Proposed solution:
  Immediately after tapping a network, even before putting it on top of the 
list, give it an indication of "trying to connect" either by a different color, 
a loading icon, ... (let the design guys figure this out)

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

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


[Touch-packages] [Bug 1888091] Re: Deform switch in the Livepatch tab

2020-07-19 Thread Matthew Paul Thomas
Well spotted, thanks.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  Deform switch in the Livepatch tab

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  When the user isn't signed in, the switch looks deform / squeezed. See
  the attached screenshot.

  Maybe the blue spinner is somehow calculated into the padding and when
  the spinner is gone (after "Checking availability"), the padding does
  not match and the switch gets squeezed.

  This is only a visual bug, non critical, but should be low hanging
  fruit.

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

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


[Touch-packages] [Bug 1402298] Re: Two independent instances of Software & Updates

2020-05-11 Thread Matthew Paul Thomas
*** This bug is a duplicate of bug 523755 ***
https://bugs.launchpad.net/bugs/523755

** This bug has been marked a duplicate of bug 523755
   Launching twice results in duelling copies

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

Title:
  Two independent instances of Software & Updates

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  software-properties-gtk:
Installed: 0.92.37.2

  What I expected to happen
  A change in the settings of Software & Updates opened through the menu of 
Synaptics Package Manager should be reflected when opening Software & Updates 
by issuing software-properties-gtk in the terminal.

  What actually happened
  In Software & Updates opened through the menu of Synaptics Package Manager 
(Settings -> Repositories), I opened the Updates tab and changed 'When there 
are other updates:' from 'Display every two weeks' to 'Display immediately'. I 
then closed the window. In the terminal I started Software & Updates by 
executing software-properties-gtk. I went to the Updates tab and the setting 
for 'When there are other updates:' was still set to 'Display every two weeks'. 
Leaving this instance of Software & Updates open, I then opened another 
instance of Software & Updates through the menu of Synaptics Package Manager. 
Opening the Updates tab, the setting for 'When there are other updates:' was 
indeed 'Display immediately'. This demonstrates that Ubuntu stores two 
independent sets of settings for Software & Updates. However, the settings 
through the menu of Synaptics are ignored by the system. This can confuse a 
user who discovers Software & Updates through the Synaptics menu and relies on 
it to customize updates.

  I will include a screen shot of these two instances of Software &
  Updates open side by side reflecting their divergent settings. Both
  windows were opened and the Updates tab chosen. No menu items were
  changed before taking the screen shot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.2
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 13 22:54:50 2014
  InstallationDate: Installed on 2014-07-01 (165 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

2020-03-16 Thread Matthew Paul Thomas
A revision of the label I mentioned above has now been implemented:
“Snap package updates are checked routinely and installed
automatically.”

In  I wrote: “Sometimes I
design things in the hope that someone will implement them someday. I
haven’t had time to do that with this dialog. But if anyone here is
interested, a simple first step — useful and releasable by itself —
would be to add a caption below the new label, of the form ‘Last check:
Yesterday 16:27’. If someone submits a merge proposal to do that, then
I’ll design the next bit.”

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

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


[Touch-packages] [Bug 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

2019-11-05 Thread Matthew Paul Thomas
** Package changed: ubuntu => software-properties (Ubuntu)

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

Title:
  Stuck at "Refreshing software cache" after enabling repository not
  updated for Eoan

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Software and Updates
  2. Go to "other software" and enable, for example, a repository disabled 
during upgrade to Eoan which is not updated for Eoan yet
  3. Press close and then reload on the dialog that opens.
  4. Refreshing software cache dialog is stuck

  After closing the dialogs by right clicking on the windows and the
  open apps bar, re opening Software and updates only shows a white
  square you can't interact with.

  Ubuntu 19.10

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

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


[Touch-packages] [Bug 1846180] Re: 1910 software-properties larger screen size

2019-10-04 Thread Matthew Paul Thomas
** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  1910 software-properties larger screen size

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  Screen size 1366x768, Russian language.

  Update settings go beyond the edge of the screen. The window cannot be
  reduced.

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

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


[Touch-packages] [Bug 1846180] Re: 1910 software-properties larger screen size

2019-10-04 Thread Matthew Paul Thomas
Barabazon, thanks for this report.

This bug would have been avoided by my design from 2016 that combines
the “Ubuntu Software”, “Other Software”, and “Authentication” tabs into
a single “Channels” tab.


As a short-term fix, perhaps the Russian translators could reduce the
problem by using shorter strings for the tab labels. For ample,
“Программное обеспечение Ubuntu” could be just “Ubuntu”, and
“Дополнительные драйверы” could be just “Драйверы”.

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

Title:
  1910 software-properties larger screen size

Status in software-properties package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  Screen size 1366x768, Russian language.

  Update settings go beyond the edge of the screen. The window cannot be
  reduced.

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

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


[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

2019-09-27 Thread Matthew Paul Thomas
That is much better, thank you. The spacing issue is still there, but
that is the least important.

(It’s also unfortunate that checkbox captions aren’t disabled when the
labels are, but that’s outside the scope of adding ZFS.)

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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


[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

2019-09-27 Thread Matthew Paul Thomas
Unfortunately this layout is highly misleading.

It’s misleading for the “Encrypt” and “Use LVM” checkboxes to be aligned
with the radio buttons above it. That suggests that they are independent
of the radio buttons. And it suggests that the radio button group has
finished. Neither is the case. This can be fixed by indenting those two
options so that they are aligned with the label of the “Replace Windows
with Ubuntu” option that they depend on.

Less importantly, it’s misleading to have *more* space between “Replace
Windows with Ubuntu” and the two options that actually depend on it,
than between it and the “Install Ubuntu alongside Windows” option that
it’s exclusive with. The simplest fix is for the spacing to be the same.

Finally, it’s misleading for any options to come after “Something else”.
The word “else” refers to things that come before it. So “Something
else” should always be the last option.

Fixing those three problems would have a bonus benefit that neither of
the separators would be needed any more.

If it’s also possible to change the wording at this late stage, please
stop using the phrase “the new installation” three times. Delete both
occurrences of “with the new installation”.

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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


[Touch-packages] [Bug 1839756] Re: Nvidia driver options are not easy to understand

2019-08-12 Thread Matthew Paul Thomas
** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Nvidia driver options are not easy to understand

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  I have just upgraded to Ubuntu 18.04.3LTS, and the options I have for
  my nvidia driver are shown in the screenshot.

  I dont understand why I have the option for an older, untested version
  of the driver as well as the latest version. Also, the wording of
  these options is highly technical and not very meaningful to someone
  who just wants the latest driver.

  I would be better to have just 2 options, with labels more meaningful to the 
end user like:
  * Latest official Nvidia driver (proprietary)
  * Latest Nouveau driver (open source)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.9
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 11 13:32:43 2019
  InstallationDate: Installed on 2016-11-11 (1002 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (351 days ago)

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

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


[Touch-packages] [Bug 1839756] Re: Nvidia driver options are not easy to understand

2019-08-11 Thread Matthew Paul Thomas
Hi mark, thanks for your report. We plan to improve this interface for
Ubuntu 19.10, as part of the inclusion of Nvidia drivers in the official
Ubuntu repositories.

I think the issue you are seeing, with a newer driver showing as
“tested” while an older one is not, is that the older one is what Nvidia
calls the “Long Lived” driver and the newer one the “Short Lived”, which
people choose depending on whether they want stability, compatibility
with the latest game updates, etc. So it’s not simply a case of “newer ×
tested” >> “older × untested”. When I designed the current UI, in
January 2012, that distinction had existed for only four months and I
wasn’t aware of it. Now, we’ll show Nvidia’s “Long Lived” and “Short
Lived” terminology in the GUI.

At the same time, as you suggested, we’ll drop technical wording that
doesn’t help you make a choice, like “metapackage” and “X.org X server”.

Here’s the new design:


** Changed in: software-properties (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  Nvidia driver options are not easy to understand

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  I have just upgraded to Ubuntu 18.04.3LTS, and the options I have for
  my nvidia driver are shown in the screenshot.

  I dont understand why I have the option for an older, untested version
  of the driver as well as the latest version. Also, the wording of
  these options is highly technical and not very meaningful to someone
  who just wants the latest driver.

  I would be better to have just 2 options, with labels more meaningful to the 
end user like:
  * Latest official Nvidia driver (proprietary)
  * Latest Nouveau driver (open source)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.9
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 11 13:32:43 2019
  InstallationDate: Installed on 2016-11-11 (1002 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (351 days ago)

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

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


[Touch-packages] [Bug 1069285] Re: Unnecessary horizontal scrolling in Additional Drivers page

2019-07-16 Thread Matthew Paul Thomas
Spec updated
:
“The listbox should not scroll horizontally; each radio button label
should wrap to multiple lines if necessary.”

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Unnecessary horizontal scrolling in Additional Drivers page

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  The Additional Drivers page generally has a short list containing
  options with long labels, such as "Using X.Org X server - AMD/ATI
  display driver wrapper from xserver-xorg-video-ati (open source,
  tested)". Some of these labels are very similar for the first 50
  characters or so.

  Many labels go well beyond the default width for the dialog, resulting
  in a horizontal scrollbar. Meanwhile, there is all sorts of vertical
  space that could easily accommodate the information. It would be
  easier to work with this dialog if the labels were word wrapped,
  instead.

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

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


[Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

2019-07-04 Thread Matthew Paul Thomas
The snap-related feature is already implemented, and other issues
concerning the settings GUI are tracked here, so I think this is the
appropriate place for it.

Currently, my design for the update settings starts with a line of
static text:

  Snap packages check for updates four times daily, downloading
automatically.

  For other packages…

There I’m trying to convey that the “Check for updates automatically:”
menu below applies to other packages, not snaps.


I intended that eventually, that line of text would become interactive —
perhaps a menu, followed by another menu or timepickers depending on the
setting, for example:

  Snap packages check for updates: [Every day:^] [4 times daily :^]

  Snap packages check for updates: [Weekdays :^] [between :^] [18:15]
and [19:00]

  Snap packages check for updates: [Custom schedule (“fri5,23:00-01:00”)
:^]

(It’s unfortunate that we need separate settings GUI for snap and deb
updates at all — mainly because snap updates are fully automatic, while
prompting for deb updates that often would be unpleasant. Perhaps we can
combine *some* of the settings in future. But since snaps and debs have
independent configuration under the hood, we’d still need to deal with
cases where their equivalent settings are currently set to different
values.)

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

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


[Touch-packages] [Bug 1549733] Re: SystemSettings Language view: hitting Space on HW keyboard triggers switch even when it (or its list item) does not show any visual focus frame

2019-04-30 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  SystemSettings Language view: hitting Space on HW keyboard
  triggers switch even when it (or its list item) does not show any
  visual focus frame

Status in Canonical System Image:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  Nexus7, rc-proposed, r373
  Ubuntu UI Toolkit version r1795

  1) Connect bluetooth keyboard
  2) Open system settings
  3) Open Language & Text view
  4) Press tab until the n-th switch shows its focus frame
  5) Now tap (using touchscreen) on the m-th list item, with  m < n (tap on the 
list item, not on the switch of that list item)
  NOTE: It is important that m < n, the bug will not trigger on listitems that 
have not been focused at least once!
  6) At this point the focus frame around the n-th switch has disappeared
  7) Now press Space on the keyboard

  Expected outcome:
  Nothing, because there is no focus frame anywhere on the screen
  This is confusing for the user as he can never be sure about which item will 
be actioned by the keyboard keys

  Actual outcome:
  The switch of the m-th list item is triggered, even though that list item or 
switch were not showing any focus frame

  : “To avoid errors from unintended focus and
  distraction from irrelevant focus rings, there should be three classes
  of control: … • Non-pointer-focusable: Focusable with Tab … Yes …
  Focusable with pointing device … No”

  : “To avoid distraction from irrelevant
  selection, there should be three classes of list: … • Non-pointer-
  selectable: Selectable with arrow keys … Yes … Selectable with
  pointing device … No … Any list that is non-pointer-selectable should
  be non-pointer-focusable.”

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

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


[Touch-packages] [Bug 1438162] Re: [osk] Touching "world" icon on the keyboard should cycle through all active keyboard layouts

2019-04-30 Thread Matthew Paul Thomas
** Description changed:

  I have 3 keyboard layouts active: English, Polish, Emoji. Now let's say
  the current layout is English. When I touch on the "world" icon the
  keyboard, the layout changes to Emoji. When I touch the icon again, the
  layout changes back to English. Then I touch it again, I get Emoji and
  so on. There's no way to change to the third layout without longpressing
  on the "world" icon and selecting the right layout there. I would expect
  the layout change to go through all active layouts, in my example
  English->Polish->Emoji->English and so on.
+ 
+ : “If you
+ tap on the button, it should cycle through layouts in order of how
+ recently you entered a character using each one.”

** No longer affects: ubuntu-ux

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

Title:
  [osk] Touching "world" icon on the keyboard should cycle through all
  active keyboard layouts

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  I have 3 keyboard layouts active: English, Polish, Emoji. Now let's
  say the current layout is English. When I touch on the "world" icon
  the keyboard, the layout changes to Emoji. When I touch the icon
  again, the layout changes back to English. Then I touch it again, I
  get Emoji and so on. There's no way to change to the third layout
  without longpressing on the "world" icon and selecting the right
  layout there. I would expect the layout change to go through all
  active layouts, in my example English->Polish->Emoji->English and so
  on.

  : “If you
  tap on the button, it should cycle through layouts in order of how
  recently you entered a character using each one.”

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

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


[Touch-packages] [Bug 1287210] Re: [system settings] No indication that Wi-Fi is available ("Prompt when not connected")

2019-04-30 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  [system settings] No indication that Wi-Fi is available ("Prompt when
  not connected")

Status in indicator-network package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Trusty r188

  0. If you haven't already, connect to a Wi-Fi network.
  1. In System Settings > Wi-Fi, turn off Wi-Fi.
  2. Turn off "Auto-join previous networks".
  3. Switch from System Settings to anything else.
  4. Turn on Wi-Fi.

  What happens: Nothing.

  What should happen: You're prompted to join the previously used Wi-Fi
  network.

  : "A
  prompt should appear, suggesting that you connect to Wi-Fi, if all of
  these conditions are true..."

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

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


[Touch-packages] [Bug 1511015] Re: [pocket pc] No option to keep app launcher visible

2019-04-30 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  [pocket pc] No option to keep app launcher visible

Status in Canonical System Image:
  Fix Released
Status in Canonical Pocket Desktop:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The app launcher auto-hides and there doesnt seem to be an option to
  keep it visible. no so much a bug but missing feature.

  : “The
  ‘Launcher & Menus’ panel should be present only when any of the
  settings apply…”

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

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


[Touch-packages] [Bug 1352784] Re: GPS indicator does not disappear when location services disabled, but bluetooth indicator does disappear when disabled.

2019-04-30 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  GPS indicator does not disappear when location services disabled, but
  bluetooth indicator does disappear when disabled.

Status in platform-api:
  Invalid
Status in indicator-location package in Ubuntu:
  Invalid
Status in platform-api package in Ubuntu:
  Invalid

Bug description:
  There is inconsistency between the bluetooth indicator and the
  location indication. Currently (image #171):

  - if location+GPS are disabled, the indicator persists.
  - if bluetooth is disabled, it disappaears.

  Which behaviour is correct?

  Further, even if the location indicator behaviour is correct, surely
  we should consider "greying out" the indicator so that the user can
  see at a glance that that indicator is disabled?

  
  Desired resolution: either implement the new indicators access method (bug 
1368856); or hide the location indicator altogether until it can be implemented 
as specced; or both.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1352784/+subscriptions

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


[Touch-packages] [Bug 1396208] Re: Pressing volume key doesn't restore full screen brightness

2019-04-30 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  Pressing volume key doesn't restore full screen brightness

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  1. Let device sit idle until the screen dims (not off, just dim)
  2. Press a volume up/down button

  Expected behavior: Screen returns to full brightness
  Actual Behavior: No change in brightness

  Reproduced on Nex4

  : "Any input, including
  volume buttons, should cancel the lock and therefore restore the
  display."

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1396208/+subscriptions

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


[Touch-packages] [Bug 1447504] Re: Phone app: Wrong number is shown in call history

2019-04-30 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  Phone app: Wrong number is shown in call history

Status in dialer-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  arale, r180, ubuntu-touch/vivid-proposed

  Steps
  1. Launch dialer-app
  2. Input number a Chinese phone number, e.g. 18812345678, and dial
  3. End the call
  4. Review in call history
  =>
  The number is displayed as (881) 234-5678

  Expected:
  1) number should be complete whithout missing the leading "1"
  2) format should be like 188-1234-5678, or just 18812345678

  : "An international phone number should be
  presented following the E.123 format, while a domestic phone number
  should be presented following the national format for the country that
  the phone was in at the time."

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

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


[Touch-packages] [Bug 1656100] Re: Unable to remove signing keys using gnome-software-properties

2019-04-25 Thread Matthew Paul Thomas
Ian, software-properties is not mentioned on the “Pending Ubuntu Stable
Release Updates” page. 

The process for issuing a Stable Release Update is on the Ubuntu wiki.
 Even if you aren’t an Ubuntu 
developer, you could probably carry out the first three steps.

If it’s declined for an SRU, the next best option would be requesting a
backport. 

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

Title:
  Unable to remove signing keys using gnome-software-properties

Status in Ubuntu GNOME:
  Invalid
Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  I have found that on Ubuntu GNOME 16.10 with GNOME 3.22 that I am
  unable to remove signing keys in the Authentication tab. If I select a
  key I wish to remove and click the Remove button, either nothing will
  happen, or it will ask me for authentication, upon giving it the
  correct password all that will happen is it will deselect the key I
  select, but at no point will it actually remove it, which is rather
  annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 12 21:35:55 2017
  InstallationDate: Installed on 2017-01-09 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1640544] Re: "indicator-power" says "estimating" when plugged to power.

2019-04-05 Thread Matthew Paul Thomas
** Changed in: indicator-power (Ubuntu)
   Status: Won't Fix => New

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

Title:
  "indicator-power" says "estimating" when plugged to power.

Status in indicator-power package in Ubuntu:
  New

Bug description:
  There seem to be a couple of bug reports from 4 - 5 years ago,
  complaining the same thing. Looks like the bug is back in 16.10.

  ---

  >1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  16.10 (yakkety)

  >2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Installed: 12.10.6+16.10.20160708-0ubuntu1
  Candidate: 12.10.6+16.10.20160708-0ubuntu1

  >3) What you expected to happen

  The indicator should say the remaining time to be fully charged, and
  display an icon of either a charging battery, or a "power plug" (In
  case the battery is fully charged, and the machine is running on
  direct power.).

  >4) What happened instead

  The indicator just says "estimating". It doesn't display whether it is
  being charged, or running on direct power.

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

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


[Touch-packages] [Bug 1817559] Re: update-notifier ignores update-manager's settings

2019-03-01 Thread Matthew Paul Thomas
Specification updated
<https://wiki.ubuntu.com/SoftwareUpdates?action=diff=230=229>:
‘Whenever “Automatically check for updates:” is set to “Never” (so any
security updates are known from manual or previous checks), the “When
there are security updates:” menu should consist of options “Remind me
daily” (the default), “Remind me every two days”, “Remind me weekly”,
and “Remind me every two weeks”. Whenever “Automatically check for
updates:” is set to anything other than “Never”, the “When there are
security updates:” menu should instead consist of options “Display
immediately” (the default) and “Install automatically”.’

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Triaged

** Changed in: software-properties (Ubuntu)
 Assignee: Matthew Paul Thomas (mpt) => (unassigned)

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

Title:
  update-notifier ignores update-manager's settings

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  
  > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu

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

  
  > 2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center

  $ apt-cache policy update-manager
  update-manager:
Installed: 1:16.04.15
Candidate: 1:16.04.15
Version table:
   *** 1:16.04.15 500
  500 https://mirror.one.com/ubuntu xenial-updates/main amd64 Packages
  500 https://mirror.one.com/ubuntu xenial-updates/main i386 Packages
  100 /var/lib/dpkg/status
   1:16.04.12 500
  500 https://mirror.one.com/ubuntu xenial-security/main amd64 Packages
  500 https://mirror.one.com/ubuntu xenial-security/main i386 Packages
   1:16.04.3 500
  500 https://mirror.one.com/ubuntu xenial/main amd64 Packages
  500 https://mirror.one.com/ubuntu xenial/main i386 Packages

  

  Steps to reproduce:

  - Run `update-manager' manually, via `update-manager' from a terminal for 
example
  - Press "Settings..." button
  - Configure the following settings to hide all update-manager's pop-ups 
respectively:

  Automatically check for updates: Never
  When there are security updates: 
  When there are other updates: Display every two weeks
  Notify me of a new Ubuntu version: Never

  - Close settings
  - Exit `update-manager'

  
  Expected behaviour:

  - update-manager won't be checking any updates at all
  - but even if there are some "other updates" then it must be displayed not 
more often than "every two weeks"

  
  Actual behaviour:

  - update-manager checks for updates from time to time by itself
  - update-manager shows notifications *all* *the* *time*: every single day and 
much more times per day than even twice
  - update-manager keeps to show notifications even if it has been seen & 
closed manually (just because there wasn't time for maintenance window 
currently, for example)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: update-manager 1:16.04.15
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 25 16:32:29 2019
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'365'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'303'
   b'com.ubuntu.update-manager' b'launch-time' b'int64 1551101458'
  InstallationDate: Installed on 2016-07-19 (951 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1817559] Re: update-notifier ignores update-manager's settings

2019-03-01 Thread Matthew Paul Thomas
Ubuntu’s update prompt is a notification in the ordinary English sense
of the word.
<https://wiki.ubuntu.com/NotificationDesignGuidelines#Normal_window> So
I guess the dconf keys predate update-notifier’s change from using FDo
notifications to launching update-manager, but I don’t think that
requires their name or description to be changed. (It is perverse,
though, to have a boolean setting whose name starts with “no-”.)

I think the bug here is that setting “Automatically check for updates:”
to “Never” has caused “When there are security updates:” to become
blank+disabled, suggesting that there will be no prompts when really
there will be. This doesn’t happen in 14.04, so I guess someone changed
it when they realized the current menu options are only relevant to
automatic checks. But besides the case where updates became known before
you switched to “Never”, there’s a much more likely case where security
updates might be known without automatic checks: if you did a manual
check but then didn’t install them.

So, I guess the menu should instead contain options for when to remind
you about known security updates that aren’t installed yet, no matter
how that happened. Anyone who’s seen a billboard or digital sign defaced
by a giant Windows update prompt might think “Never” should be one of
the options, but I’ll defer to Steve that it shouldn’t be. (I guess we’d
say that kind of thing should use Ubuntu Core instead.)

** Changed in: software-properties (Ubuntu)
   Status: New => In Progress

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Matthew Paul Thomas (mpt)

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

Title:
  update-notifier ignores update-manager's settings

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  
  > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu

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

  
  > 2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center

  $ apt-cache policy update-manager
  update-manager:
Installed: 1:16.04.15
Candidate: 1:16.04.15
Version table:
   *** 1:16.04.15 500
  500 https://mirror.one.com/ubuntu xenial-updates/main amd64 Packages
  500 https://mirror.one.com/ubuntu xenial-updates/main i386 Packages
  100 /var/lib/dpkg/status
   1:16.04.12 500
  500 https://mirror.one.com/ubuntu xenial-security/main amd64 Packages
  500 https://mirror.one.com/ubuntu xenial-security/main i386 Packages
   1:16.04.3 500
  500 https://mirror.one.com/ubuntu xenial/main amd64 Packages
  500 https://mirror.one.com/ubuntu xenial/main i386 Packages

  

  Steps to reproduce:

  - Run `update-manager' manually, via `update-manager' from a terminal for 
example
  - Press "Settings..." button
  - Configure the following settings to hide all update-manager's pop-ups 
respectively:

  Automatically check for updates: Never
  When there are security updates: 
  When there are other updates: Display every two weeks
  Notify me of a new Ubuntu version: Never

  - Close settings
  - Exit `update-manager'

  
  Expected behaviour:

  - update-manager won't be checking any updates at all
  - but even if there are some "other updates" then it must be displayed not 
more often than "every two weeks"

  
  Actual behaviour:

  - update-manager checks for updates from time to time by itself
  - update-manager shows notifications *all* *the* *time*: every single day and 
much more times per day than even twice
  - update-manager keeps to show notifications even if it has been seen & 
closed manually (just because there wasn't time for maintenance window 
currently, for example)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: update-manager 1:16.04.15
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 25 16:32:29 2019
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'365'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'303'
   b'com.ubuntu.update-manager' b'launch-time' b'int64 1551101458'
  InstallationDate: Installed on 2016-07-19 (951 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
h

[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04

2019-03-01 Thread Matthew Paul Thomas
Oi Edson

I don’t know what you mean by “efficiency test”. But to answer your
question, these are the use cases we were designing for:

- Someone was using Livepatch in 18.04 LTS, then they upgraded to 19.04,
and they skipped past (or forgot) the warning that Livepatch wouldn’t be
available after they upgraded, and now they are wondering what’s going
on.

- Someone is already using 19.04 when someone tells them about
Livepatch, and they don’t know that it’s LTS-only, so they go searching
for it in the GUI.

For these cases, the previous behavior — simply hiding the tab
altogether — was not helpful. The drawback is that for as long as you
keep using non-LTS releases, there will be one tab of stuff that you
can’t use. But since that is just one tab in a settings window, I think
it’s worthwhile.

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

Title:
  Livepatch is not available for this system Ubuntu Disco 19.04

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Hi guys

  There is an option for livepacth, but there is information that is not
  yet available for Ubuntu Disk 19.04. Will the livepatch be available
  for Ubuntu Disk 19.04?

  "Livepacth is not available for this system"

  See attached

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: software-properties-gtk 0.97.6
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 14:08:04 2019
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-02-11 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04

2019-02-28 Thread Matthew Paul Thomas
Edson, apart from the theme and locale, that looks the same as Andrea’s
screenshot of the intended behavior.

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

Title:
  Livepatch is not available for this system Ubuntu Disco 19.04

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Hi guys

  There is an option for livepacth, but there is information that is not
  yet available for Ubuntu Disk 19.04. Will the livepatch be available
  for Ubuntu Disk 19.04?

  "Livepacth is not available for this system"

  See attached

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: software-properties-gtk 0.97.6
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 14:08:04 2019
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-02-11 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1798839] Re: Canonical Livepatch doesn't appear in "Updates" tab.

2018-10-22 Thread Matthew Paul Thomas
I’ve reported bug 1799310 about warning you when an upgrade will result
in Livepatch no longer being available.

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

Title:
  Canonical Livepatch doesn't appear in "Updates" tab.

Status in software-properties package in Ubuntu:
  New

Bug description:
  Livepatch was working and appearing fine in 'Software & Updates' until
  after the upgrade from Ubuntu 18.04 LTS to Ubuntu 18.10; Livepatch
  does not appear as an option anymore after upgrading.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-gtk 0.96.27
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 11:04:03 2018
  InstallationDate: Installed on 2018-08-17 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

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

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


[Touch-packages] [Bug 1545118] Re: [AdaptivePageLayout] can't easily grab scrollbar if dual column

2018-06-22 Thread Matthew Paul Thomas
I agree that this solution is “complex and error prone”. Any solution
would balance those; I chose more complexity for fewer errors.

However, while I used the phrase “touch area” rather than “target area”,
nothing in the solution I gave is inapplicable to a mouse. It should all
work exactly the same with mouse input.

** No longer affects: ubuntu-ux

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

Title:
  [AdaptivePageLayout] can't easily grab scrollbar if dual column

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

Bug description:
  If you have an app that uses AdaptivePageLayout and supports 2
  columns, if there is a scrollbar in the first column, it's very
  difficult to grab it with your mouse because when you get close to it,
  you get the horizontal arrows showing to allow resizing of the panels
  in the multi-column layout.

  You can try this with messaging-app in silo 30 (soon to land)

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

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


[Touch-packages] [Bug 1534191] Re: video replay should resume after user confirms high volume

2018-02-20 Thread Matthew Paul Thomas
** Changed in: indicator-sound (Ubuntu)
 Assignee: Matthew Paul Thomas (mpt) => (unassigned)

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

Title:
  video replay should resume after user confirms high volume

Status in indicator-sound package in Ubuntu:
  Incomplete
Status in mediaplayer-app package in Ubuntu:
  Confirmed

Bug description:
  A followup to bug #1504065 suggested by davmor2 in #phablet.

   charles, jhodapp: with silo 46 I have an issue. On first
  boot and possibly every day after that, if you try and watch a video
  from the device, you get a popup saying audio is loud accept or what
  ever, this popup takes focus from the media player and therefore
  pauses the video, when you click on yes is there a way we can continue
  playback for the audio warnings?

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

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


[Touch-packages] [Bug 629258] Re: Battery life estimation never comes around

2018-02-19 Thread Matthew Paul Thomas
This bug was fixed over six years ago. If you experience similar systems
on multiple operating systems, contact your PC vendor. Otherwise, report
a separate bug.

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

Title:
  Battery life estimation never comes around

Status in DeviceKit-Power:
  Fix Released
Status in gnome-power:
  Invalid
Status in One Hundred Papercuts:
  Invalid
Status in System76:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in upower source package in Maverick:
  Won't Fix

Bug description:
  Binary package hint: gnome-power-manager

  When running on battery, the mouse over text for the battery icon (when 
running on battery) permanently says "Battery life (estimating...)". An 
estimate never shows up.
  Computer: HP Envy 14

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-power-manager 2.31.90-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-19.28-generic-pae 2.6.35.3
  Uname: Linux 2.6.35-19-generic-pae i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Fri Sep  3 06:38:47 2010
  ExecutablePath: /usr/bin/gnome-power-manager
  GConfNonDefault:
   /apps/gnome-power-manager/lock/blank_screen=false
   /apps/gnome-power-manager/lock/use_screensaver_settings=false
   /apps/gnome-power-manager/notify/sleep_failed_uri=
   /apps/gnome-power-manager/ui/icon_policy=charge
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  MachineType: Hewlett-Packard HP ENVY 14 Notebook PC
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic-pae 
root=UUID=76ae939d-2ce2-466e-88d5-98b11aad6098 ro quiet splash
  ProcEnviron:
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  dmi.bios.date: 07/21/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1436
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 59.20
  dmi.chassis.asset.tag: CNU0274F2B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.12:bd07/21/2010:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr0492102419162:rvnHewlett-Packard:rn1436:rvr59.20:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 14 Notebook PC
  dmi.product.version: 0492102419162
  dmi.sys.vendor: Hewlett-Packard

  See also bug #629257 (one lower) for previous (lukewarm) discussions
  on the implications of showing "(estimating...)" via the user
  interface. This two bugs might want re-splitting/sorting again based
  on those that relate to the chrono estimate not being known, and those
  that relate to the pointless display of that unknown data for long
  periods of time to the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devicekit-power/+bug/629258/+subscriptions

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


[Touch-packages] [Bug 1650022] Re: We need a "close" action for killing an app in a trust prompt

2018-02-16 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  We need a "close" action for killing an app in a trust prompt

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

Bug description:
  The original designs for trust prompts included a close action in the
  header to close apps that were opened in a trust session.  This is
  particularly important when apps might not behave well or hang, there
  is no way out.  The close action is like a back button to take you
  back out of the app.

  We're close to landing trust session support in content-hub, where
  we'll open source apps for content picking in a trust prompt.  We've
  found apps that have a tendency to hang, leaving the user no way out
  besides killing both the source and destination apps.  Clearly those
  apps need some fixing, but we need to give the user an easy way out.

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

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


[Touch-packages] [Bug 1497093] Re: [Window management] Window resize grab area is too small (too hard to find) under Unity8

2017-11-29 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  [Window management] Window resize grab area is too small (too hard to
  find) under Unity8

Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The window resize grab area is too small (too hard to find) under
  Unity8. It usually takes a few attempts clicking around the shadow
  region of a window before I land on a spot where resizing works.

  See also: The Mir board in Trello where I've outlined related future
  enhancements Mir needs to support this properly.

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

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


[Touch-packages] [Bug 1317860] Re: the phone should switch itself off before completely draining battery

2017-11-28 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  Fix Released
Status in indicator-power package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Invalid

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

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

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


[Touch-packages] [Bug 1268097] Re: [System settings] Can't set user-supplied ring tone

2017-11-28 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  [System settings] Can't set user-supplied ring tone

Status in Canonical System Image:
  Fix Released
Status in content-hub package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  AFAICS I can't set a custom ring tone without using a writable image.
  (http://askubuntu.com/questions/372759/ringtones-in-ubuntu-touch)

  : "In the “Ringtone”
  screen, immediately before “None” should be a “Custom Ringtone…”
  item..."

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

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


[Touch-packages] [Bug 1370008] Re: URL Dispatcher Should Prompt on Bad URL

2017-11-28 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  URL Dispatcher Should Prompt on Bad URL

Status in Canonical System Image:
  Confirmed
Status in url-dispatcher package in Ubuntu:
  Fix Released

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

  : "Whenever
  the URL dispatcher is called on to open an address of a protocol that
  it does not understand (url-dispatcher-bad-url), it should open an
  alert with the title “Unrecognized Address”, text of the form ‘Ubuntu
  can’t open addresses of type “{protocol:}”.’, and an “OK” button. To
  prevent denial of UI service, however, the alert should not open if it
  has already opened more than three times in the past minute."

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

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


[Touch-packages] [Bug 1364452] Re: People's own phone number isn't where they expect to find it

2017-11-28 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  People's own phone number isn't where they expect to find it

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Twenty people were given an Ubuntu phone and asked to find their own
  phone number. (10 were iPhone users, 8 Android, 1 Windows Phone, and 1
  feature phone user.)

  The first place they looked:
  - 9 in the Contacts app
  - 5 in System Settings "Phone" screen
  - 3 in System Settings "About" screen
  - 2 in the Dialer app contacts screen
  - 1 in System Settings "Cellular" screen.

  So, our current placement of the phone number in the "About" screen
  (bug 1221908) is suboptimal.

  Instead it should be in the Contacts app, and possibly in the "Phone" screen.
  Where the phone is dual SIM, both phone numbers should be shown.

  Only once that is done, it should be removed from the "About" screen.

  : "Address Book should always contain one
  special contact representing you as the user of the phone ... To
  indicate its purpose and resilience, the “Me” contact should be
  denoted by the word “Me” as a caption at the trailing end (with a
  translation hint stating that it should be extremely short); and the
  contact’s visual design should be subtly different from other
  contacts. Apart from those two differences, the contact should be
  displayed and ordered the same as any other contacts in the list..."

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

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


[Touch-packages] [Bug 1378350] Re: Need to allow multiple apps to handle the same url patterns

2017-11-28 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  Need to allow multiple apps to handle the same url patterns

Status in Canonical System Image:
  Confirmed
Status in content-hub package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in url-dispatcher package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * install gmail and dekko apps

  Expected:
  * when using a mailto: URL (see bug #1351222) URL, the user should be asked 
which app to open (and cache the response optionally?)

  Current:
  * not sure what would happen ;)

  Design resolution _

  Case 1: If no email client is installed and a user clicks on a 'mail
  to' link, the user should be prompted to download the Dekko app.

  Case 2: If the user has Dekko installed, then clicking on the 'mail
  to' link should open the Dekko client --> compose mail screen to the
  'mail to' address.

  Case 3: If the user has Dekko and Gmail installed, the 'mail to' link
  by default should open in the Dekko client. However, the user can
  change their mail client preferences in system settings.

  Case 4: If the user has Gmail and another mail client installed, the
  'mail to' link should default to the first client that was installed
  on their device (which would be the default mail client preference in
  system settings -  this can be changed by the user via system
  settings).

  Notes:
  1. Wherever the user has not actively changed a mail client preference and 
Dekko is installed on their device, the default 'mail to' client should be 
Dekko.
  2. When clicking on a 'mail to' link, the user's expectation is to have this 
link open in a relevant client (unless it is case 1), therefore this should be 
the case and any mail preference choices the user can perform via system 
settings rather than being presented with multiple choice options of which 
client to open the URL in.

  : "Whenever the URL dispatcher
  is called on to open an address that multiple apps have registered
  for, it should open a “Use App” dialog, with a centered grid of
  labelled buttons with the icon for each applicable app, followed by a
  “Cancel” button."

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

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


[Touch-packages] [Bug 1357548] Re: [toolkit] Empty PIN/password/passphrase field appears to contain 4 characters

2017-11-28 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  [toolkit] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in Canonical System Image:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu RTM:
  Fix Released

Bug description:
  minor interrelated issues & probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 "bullets" implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the "bullets" remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a "show password" would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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


[Touch-packages] [Bug 1385410] Re: hook into system-image updates to precompile policy prior to reboot

2017-11-28 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  hook into system-image updates to precompile policy prior to reboot

Status in click-apparmor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Occasionally users will receive and OTA update that requires apparmor
  policy to be recompiled. Recompiling apparmor policy can take quite a
  bit of time (minutes) depending on how many applications the user has
  installed. While this is only expected to happen on major OTA OS
  upgrades (eg, 14.10 to 15.04), it is possible it could happen at other
  times. This would improve the user experience for developers
  considerably since policy recompiles can be relatively frequent when
  running the development release.

  : "On start
  apparmor profiles need to be regenerated which means the first boot
  after the upgrade might take long depending on the number of installed
  applications (even up to 30 minutes). Currently there will be no
  visual indication of the profile regeneration, so please be patient
  and wait until you see the UI appearing."

  To improve the user experience, we should detect and recompile
  apparmor profiles prior to reboot but after system-image updates has
  downloaded the new update. This always for the possibility of using a
  progress meter when compiling policy (which we currently cannot).

  :
  "Therefore, every step of the system update should show a progress
  bar, that fills once across all the steps ... Subtask Recompiling
  apparmor profiles; Allocation 45%; Resulting range 0~45%"

  See also bug 1350598, about caching compiled policies more often.

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

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


[Touch-packages] [Bug 1710377] Re: "Additional Drivers" desktop shortcut missing in Ubuntu 17.10

2017-10-15 Thread Matthew Paul Thomas
That “Additional Drivers” has its own .desktop file at all is the result
of two ancient accidents.

First, it dates from 2008, before Ubuntu gained a unified System
Settings utility. 

And second, Additional Drivers was merged into Software & Updates Settings, but 
nobody has yet taken the next step of integrating Software & Updates Settings 
into System Settings.


But as long as you can access it *from* System Settings (and as well as
from Software Updater and Gnome Software), I don’t think it’s
appropriate for it to have a .desktop file at all. That it’s a separate
app is a technical detail.

FWIW, I said much the same thing more than ten years ago.


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

Title:
  "Additional Drivers" desktop shortcut missing in Ubuntu 17.10

Status in software-properties package in Ubuntu:
  New

Bug description:
  There used to be an "Additional Drivers" shortcut in the applications
  list in Unity. This shortcut is missing in the GNOME Shell Overview in
  Ubuntu 17.10.

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

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


[Touch-packages] [Bug 1363214] Re: [System Settings] [design] allow Passcodes of variable length instead of just 4 digits

2017-09-22 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  [System Settings] [design] allow Passcodes of variable length instead
  of just 4 digits

Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Currently when setting a Passcode on the device, it must be 4 digits.
  This is artificially limiting. Other platforms (eg Android) allow
  longer Passcodes. It has always been my understanding that we should
  support Swipe, Passphrase and Passcode where Passphrase and Passcode
  can be arbitrarily long.

  However, once longer Passcodes are supported, we will have to add an
  Enter key. Right now, the lockscreen checks the Passcode once 4 digits
  are added so that you don't have to press Enter. I guess this was done
  for usability, but would be a security issue because an attacker can
  easily determine the Passcode length, which makes it easier to for an
  attacker to guess the Passcode. Eg, if I have a 5 digit Passcode set,
  then an attacker need only type '1' and know that the Passcode is
  only five characters. Now, a Passcode isn't strong to begin with and
  an automated attack could rather quickly brute force Passcodes, but we
  shouldn't make it easier for someone manually trying to guess the
  Passcode.

  The passphrase lockscreen prompt correctly allows variable length
  passphrases and requires you to press Enter.

  I suggest moving the 'X' up t the left of '0' and an Enter symbol to
  the rigth of '0'.

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

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


[Touch-packages] [Bug 1714766] Re: Software center apt failure at 15% when loading programs

2017-09-04 Thread Matthew Paul Thomas
** Package changed: software-center (Ubuntu) => apt (Ubuntu)

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

Title:
  Software center apt failure at 15% when loading programs

Status in apt package in Ubuntu:
  New

Bug description:
  I have just loaded the Ubuntu from LINUX format July 2017 edition,
  onto my wifes computer. I tried to load a DVD player onto the computer
  (a Lenovo ideapad 305) and every program that I try fails at 15% with
  an error "apt exception failure", I have since gone to the room above
  the room I was in (where the router is) and have managed to load VLC
  player without a problem. Any ideas why and how I can make it easier
  to use WiFi in all rooms in my semi-detached 3 bed house. I wondered
  if it was the software or the computer (which has just been bought,
  pre-installed with Windows 10. Widows 10 has been totally removed as
  it refused to allow dual boot.

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

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


[Touch-packages] [Bug 1133107] Re: Hidden Microsoft ULA when installing Ubuntu Restricted Extras

2017-07-25 Thread Matthew Paul Thomas
** Changed in: debconf (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: software-center (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Hidden Microsoft ULA when installing Ubuntu Restricted Extras

Status in debconf package in Ubuntu:
  Confirmed
Status in software-center package in Ubuntu:
  Triaged

Bug description:
  64-bit  3.8.0-7-generic #15-Ubuntu SMP Thu Feb 21 20:07:18 UTC 2013

  1. Launch Unbuntu Software Center.
  2. Begin installation of Ubuntu Restricted Extras.
  3. Application will appear to hang after a while.
  4. Popup displaying the Microsoft ULA is not being brought to the top so the 
app waits patiently for user input.

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

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


[Touch-packages] [Bug 1685934] Re: ok button duplication

2017-06-26 Thread Matthew Paul Thomas
** Changed in: indicator-datetime (Ubuntu)
   Status: Expired => New

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

Title:
  ok button duplication

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  I think redundancy is often good but not for UI elements, see the
  attached screenshot.

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

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


[Touch-packages] [Bug 1588357] Re: no character count in messaging app

2017-06-23 Thread Matthew Paul Thomas
*** This bug is a duplicate of bug 1278790 ***
https://bugs.launchpad.net/bugs/1278790

** No longer affects: indicator-messages (Ubuntu)

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

Title:
  no character count in messaging app

Status in messaging-app:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  when you are typing a text message in the messaging application there
  is no character counter to tell you how many sms messages will be
  required to send the message.

  expected behaviour would be a counter while you type your message such
  as:

  12/140

  would show you have used 12 characters out of a total of 140
  available.

  ps. I have no idea what the actual limit is and I think it might be
  different in different countries.

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

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


[Touch-packages] [Bug 393585] Re: Focused/unfocused selection colors are confusingly similar

2017-06-05 Thread Matthew Paul Thomas
ubuntu-ux was a dummy project for the purpose of getting the opinion of
Canonical’s platform design team. That team no longer exists. My view on
this, however, is the same as it was when I commented in April 2010.

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

Title:
  Focused/unfocused selection colors are confusingly similar

Status in One Hundred Papercuts:
  Invalid
Status in community-themes package in Ubuntu:
  Opinion
Status in nautilus package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Opinion

Bug description:
  Problem occurs with: Ambiance, Radiance, Clearlooks, DarkRoom,  Dust, 
Elementary, Glossy, Human, Human-Clearlooks
  Does not occur with: New Wave

  For example, open a Nautilus window and select an icon.  Switch focus
  to the desktop by clicking on it.  The window is not active but the
  icon in it retains the "selected items" color.  It appears as though
  it is still selected and that it can be modified by keyboard
  shortcuts.  By clicking on an icon on the desktop it changes color to
  be selected an now it appears that two items are selected.

  Several times I've deleted things by accident due to this, especially
  when I was new to GNOME.  I would have several windows open with items
  selected.  I would see the item I want selected and hit the delete key
  to remove it, only to realize that I had some other window focused
  where I had deleted something else.

  In Windows selected items in unfocused windows turn gray.  I think it
  also adds another visual clue as to what window is focused besides
  just the title bar.

  Firefox and Thunderbird deliver the behavior I expect (probably
  because they are only faux GTK apps).  Select some text in Firefox and
  then focus to another window and you will see that the selected text
  turns gray, indicating it is not active.  Try that in gedit or evince
  and the text will remain blue.

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

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


[Touch-packages] [Bug 1520615] Re: Use of Ubuntu logo as default app icon dilutes the brand

2017-05-26 Thread Matthew Paul Thomas
** Attachment added: "screenshot of the problem"
   
https://bugs.launchpad.net/snapstore/+bug/1520615/+attachment/4884155/+files/1520615-Ubuntu-logo-as-app-icon.cropped.png

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

Title:
  Use of Ubuntu logo as default app icon dilutes the brand

Status in Canonical System Image:
  Confirmed
Status in Click Package Index:
  Invalid
Status in Snap Store:
  Triaged
Status in Software Center Agent:
  Invalid
Status in ubuntu-sdk-ide package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Incomplete
Status in ubuntu-touch-meta package in Ubuntu:
  New

Bug description:
  Currently, MyApps and CPI are using the "placeholder-app-icon.png"
  from the Suru theme, which is a basic greyscale image, including a
  version of the Ubuntu logo. Showing this logo as the app icon for apps
  which have no icon, implies they are officially supported apps by
  Ubuntu, and dilutes the brand and trademark, when they are not
  actually such apps, particularly when they have no function directly
  linked to any part of Ubuntu.

  Instead, a better representation would be a generic representation of
  an app window or similar.

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

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


[Touch-packages] [Bug 1520615] Re: Use of Ubuntu logo as default app icon dilutes the brand

2017-05-26 Thread Matthew Paul Thomas
This is still a problem with snapstore, the sequel to MyApps.

** Project changed: ubuntu-ux => snapstore

** Changed in: snapstore
 Assignee: Matthieu James (tiheum) => (unassigned)

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

Title:
  Use of Ubuntu logo as default app icon dilutes the brand

Status in Canonical System Image:
  Confirmed
Status in Click Package Index:
  Invalid
Status in Snap Store:
  Triaged
Status in Software Center Agent:
  Invalid
Status in ubuntu-sdk-ide package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Incomplete
Status in ubuntu-touch-meta package in Ubuntu:
  New

Bug description:
  Currently, MyApps and CPI are using the "placeholder-app-icon.png"
  from the Suru theme, which is a basic greyscale image, including a
  version of the Ubuntu logo. Showing this logo as the app icon for apps
  which have no icon, implies they are officially supported apps by
  Ubuntu, and dilutes the brand and trademark, when they are not
  actually such apps, particularly when they have no function directly
  linked to any part of Ubuntu.

  Instead, a better representation would be a generic representation of
  an app window or similar.

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

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


[Touch-packages] [Bug 1317013] Re: Network indicator has mysterious "R" triangle icon

2017-05-26 Thread Matthew Paul Thomas
Since Ubuntu Phone has been retired, whether it was fixed is moot, in
both senses of the word.

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

Title:
  Network indicator has mysterious "R" triangle icon

Status in indicator-network package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Unicorn r13

  1. Flash the phone.
  2. Start up the phone.
  3. Look at the top of the screen.

  What you see: A mysterious "R" in a triangle.

  What you should see: No such icon.

  This is not in the spec and I don't know what it's for.

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

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


[Touch-packages] [Bug 1186754] Re: Use icon theme for starred icons

2017-05-26 Thread Matthew Paul Thomas
** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Use icon theme for starred icons

Status in Ubuntu theme:
  Incomplete
Status in software-center package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  As of GNOME 3.8 in Saucy, the gnome icons themes ('gnome', symbolic,
  and HighContrast) provide star icons. If Software Center would use
  these theme icons, it would provide more consistency with other apps
  that use starred rankings and should simplify the code
  (softwarecenter/ui/gtk3/widgets/stars.py).

  The icon names are
  starred
  semi-starred
  semi-starred-rtl
  non-starred

  (Although we may need to backport the semi-starred icons for the
  'gnome' theme since those are missing:
  https://bugzilla.gnome.org/689098)

  I'm adding a ubuntu-themes task to this bug as you may want to move
  the existing star icons from softwarecenter/ui/qml/ to that package.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: software-center 5.6.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sun Jun 2 11:11:51 2013
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (25 days ago)

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

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


[Touch-packages] [Bug 1186754] Re: Use icon theme for starred icons

2017-05-26 Thread Matthew Paul Thomas
Still the case in 14.04: the USC star icons are different from the
standard ones seen in Rhythmbox (for example), but the standard ones are
too nasty to use.

** Changed in: software-center (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Use icon theme for starred icons

Status in Ubuntu theme:
  Incomplete
Status in software-center package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  As of GNOME 3.8 in Saucy, the gnome icons themes ('gnome', symbolic,
  and HighContrast) provide star icons. If Software Center would use
  these theme icons, it would provide more consistency with other apps
  that use starred rankings and should simplify the code
  (softwarecenter/ui/gtk3/widgets/stars.py).

  The icon names are
  starred
  semi-starred
  semi-starred-rtl
  non-starred

  (Although we may need to backport the semi-starred icons for the
  'gnome' theme since those are missing:
  https://bugzilla.gnome.org/689098)

  I'm adding a ubuntu-themes task to this bug as you may want to move
  the existing star icons from softwarecenter/ui/qml/ to that package.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: software-center 5.6.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sun Jun 2 11:11:51 2013
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (25 days ago)

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

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


[Touch-packages] [Bug 1291458] Re: Volume buttons change ringtone volume when screen is off

2017-05-05 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  Volume buttons change ringtone volume when screen is off

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

Bug description:
  This is a rather bigger topic for user experience design, but one
  thing that should at least happen asap is volume buttons should be
  disabled when screen is off, otherwise your you-thought-silenced-phone
  suddenly blares a ring tone.

  Steps to repro:
  * suspend your phone
  * press volume buttons

  Expected result:
  * nothing happens

  Current result:
  * volume changes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140306-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Wed Mar 12 13:14:37 2014
  InstallationDate: Installed on 2014-03-12 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140312)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

  -

  : "When the screen is
  off, to minimize accidental volume changes, the keys should have
  effect only if any audio is currently playing, and they should not
  turn on the screen."

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

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


[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

2017-05-05 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

  : ‘If you
  insert a new SIM, a “Changing SIM” dialog should appear with the text
  “To use this new SIM, we need to restart.” and buttons “Later” and
  “Restart Now”.’

  Summary of required work:
   - enabling ofono hotswap support through environment variable
   - adding the modal dialog to unity8 side
   - modify i-network to detect the hotswapping and trickering
     the dialog from unity8

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

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


[Touch-packages] [Bug 1541588] Re: [System Settings] Changes needed for the UI on a tablet device

2017-05-05 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
  [System Settings] Changes needed for the UI on a tablet device

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  Note for design: can we simply avoid referring to the/this phone as in
  most uses its not necessary for clarity, and then the same text can
  always apply..

  Main panel:
  Hide Cellular
  Hide Hotspot
  Hide Phone
  About this phone -> About this device or just About
  Reset phone -> Reset device or just Reset

  Background
  Ensure default for images is landscape

  Sound:
  Hide Ringer, Phone Calls and Messages sections

  Security and Privacy
  Hide SIM PIN
  Locking and unlocking > Lock security "Unlock the phone using" --> "Unlock 
the device using"
  Locking and unlocking > Lock when idle  "Lock the phone when..." --> "Lock 
the device when ..."
  "Phone won't lock..." --> Device won't lock ..."

  About this device
  Hide IMEI
  Developer mode >  "this phone" --> "this device"

  A minor point but what happens when we search in settings for hidden
  stuff

  
  
  Note from design:

  - The text in the UI should never refer to "Phone", "Tablet" or
  "Desktop".  Instead the word "Device" should be used.

  - e.g. "About This Computer" or "About This Phone" is incorrect. This
  wording should be changed to "About this device" in both the indicator
  and System Settings to be convergence friendly.

  - This change applies to all device references in the UI.

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

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


[Touch-packages] [Bug 1668699] Re: Drop "Open a " from .desktop Actions

2017-04-03 Thread Matthew Paul Thomas
** No longer affects: ubuntu-ux

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

Title:
   Drop "Open a " from .desktop Actions

Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Start the Web Browser app.
  Right-click on its icon in Unity's Dash (the strip on the left side of the 
screen).
  There are two custom Actions: "Open a New Window" and "Open a New Private 
Window".

  I propose that the "Open a " prefix be dropped.

  This provides greater consistency with other apps which just use "New
  Window" or "New Document" Actions. Examples include epiphany-browser,
  gedit, LibreOffice and Nautilus.

  In GNOME Shell, Actions show in the Activities Overview. GNOME Shell
  includes a default "New Window" action. So in GNOME Shell, the actions
  shown include the duplicate "New Window" and "Open a New Window".
  (Note that an explicit "New Window" shortcut does not duplicate the
  default "New Window" in GNOME Shell as long as the action is named
  new-window.)

  See also LP: #1668664 for Firefox and LP: #1668730 for Chromium.

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

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


[Touch-packages] [Bug 1668699] Re: Drop "Open a " from .desktop Actions

2017-03-09 Thread Matthew Paul Thomas
As far as I can tell, this change is not in conflict with any browser
design spec, and the consistency argument makes sense. Thanks Jeremy.

** Changed in: ubuntu-ux
   Status: New => Fix Committed

** Changed in: ubuntu-ux
 Assignee: (unassigned) => Matthew Paul Thomas (mpt)

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

Title:
   Drop "Open a " from .desktop Actions

Status in Ubuntu UX:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Start the Web Browser app.
  Right-click on its icon in Unity's Dash (the strip on the left side of the 
screen).
  There are two custom Actions: "Open a New Window" and "Open a New Private 
Window".

  I propose that the "Open a " prefix be dropped.

  This provides greater consistency with other apps which just use "New
  Window" or "New Document" Actions. Examples include epiphany-browser,
  gedit, LibreOffice and Nautilus.

  In GNOME Shell, Actions show in the Activities Overview. GNOME Shell
  includes a default "New Window" action. So in GNOME Shell, the actions
  shown include the duplicate "New Window" and "Open a New Window".
  (Note that an explicit "New Window" shortcut does not duplicate the
  default "New Window" in GNOME Shell as long as the action is named
  new-window.)

  See also LP: #1668664 for Firefox and LP: #1668730 for Chromium.

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

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


[Touch-packages] [Bug 1663514] Re: Problem while installing software

2017-02-24 Thread Matthew Paul Thomas
** Project changed: canonical-identity-provider => unattended-upgrades
(Ubuntu)

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

Title:
  Problem while installing software

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Ubuntu Version:- 16.04
  Issue:

  Package:unattended-upgradees 0.90ubuntu0.3
  For more Detail Go to Attachment Image file.

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

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


[Touch-packages] [Bug 1590462] Re: Wizard city search should do searches in the middle of names

2017-02-01 Thread Matthew Paul Thomas
I’ve just discussed this with Paty and we agreed on the following.

Search should work the same way in the first-run setup as it does in
System Settings.

If those two search the same way, then comparing “the string and [any]
portions of the string” would regress bug 1454186. Fortunately, the
actual bug can be fixed without doing that (making this bug report,
incidentally, one more example of how “should” in a bug summary is
presumptive.)

In the spec for Time & Date settings I wrote: “As with any other search
field, any word you enter that is followed by a space or punctuation
should be treated as a complete word, while any word that is not should
be treated as if it might be either a complete word or the beginning of
a word.”

That wasn’t as precise as it needed to be. But I would have expected
searching “Hospitalet” to return “L'Hospitalet de Llobregat” without
doing full substring matching, because in the result it is preceded by
an apostrophe and so counts as the start of a separate “word”. Spec
updated.


** Summary changed:

- Wizard city search should do searches in the middle of names
+ City search “Hospitalet” doesn’t find  L'Hospitalet de Llobregat

** Description changed:

  The official name of my city is 
L'Hospitalet de Llobregat
  but it is often usually written as
Hospitalet de Llobregat
  
  On the wizard city/timezone selection window we only search from the 
beginning of the string so I could not find my city until i realized i may have 
to type the
L'
  at the beginning.
+ 
+ : “As with any search field,
+ any series of letters immediately followed by a space or punctuation
+ character should match only complete words, while any series of letters
+ at the end of the string should match both complete words and the
+ beginnings of words. (In the terms being searched, a “word” is a series
+ of letters that is immediately preceded by the start of the string or
+ any non-letter character, and immediately followed by the end of the
+ string or any non-letter character.)”

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

Title:
  City search “Hospitalet” doesn’t find  L'Hospitalet de Llobregat

Status in Ubuntu UX:
  Fix Released
Status in geonames package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  The official name of my city is 
L'Hospitalet de Llobregat
  but it is often usually written as
Hospitalet de Llobregat

  On the wizard city/timezone selection window we only search from the 
beginning of the string so I could not find my city until i realized i may have 
to type the
L'
  at the beginning.

  : “As with any search
  field, any series of letters immediately followed by a space or
  punctuation character should match only complete words, while any
  series of letters at the end of the string should match both complete
  words and the beginnings of words. (In the terms being searched, a
  “word” is a series of letters that is immediately preceded by the
  start of the string or any non-letter character, and immediately
  followed by the end of the string or any non-letter character.)”

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

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


[Touch-packages] [Bug 1659869] Re: Page header and focus behaviour

2017-01-27 Thread Matthew Paul Thomas
Yes, for each panel in a window, focus should go through that panel’s
header, then to the panel body (so you can select something in it if
it’s a list, or else just scroll through it), then to the panel footer
if there is one (such as the “Write a message” field). That should
happen without any effort by the app developer.

So as long as there are no messages in the message pane, focus should
flow as shown in Renato’s “expected focus path” illustration, and the
only thing the app developer should need to specify is that the “To:”
field is focused by default (otherwise the thread list would be). Once
there are messages in the message pane (for example, you’ve entered a
recipient who has previous messages), the message pane should join the
focus cycle.

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

Title:
  Page header and focus behaviour

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

Bug description:
  We have been discussing on IRC about the focus path on page header->
  page-contents.

  Some apps require a fine tuning on the focus path for the header
  buttons and contents. This is not possible today since we do not have
  access to all header objects (only actions).

  Another problem is that the page first receive focus on your contents
  and after the header. This can be annoying if the focus starts on the
  header because the focus go to another page before enter on page
  contents (check img0.png). would be nice to allow apps to choose which
  is the desired focus paths between pages and headers. (something like
  img1.png)

  And in the end would be nice to have a AdaptativePageLayout method to
  allow user to access a page based on index or something else in case
  of the user want to move focus to a different page in the stack.

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

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


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

2017-01-26 Thread Matthew Paul Thomas
Specification updated.
<https://wiki.ubuntu.com/LanguageAndText?action=diff=66=65>

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: In Progress => Triaged

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: Matthew Paul Thomas (mpt) => (unassigned)

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

Title:
  Add option for semi-transparent keyboard

Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

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

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

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

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

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


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

2017-01-26 Thread Matthew Paul Thomas
Unfortunately I don’t currently have permission to update my own design
spec. In the meantime, here’s the wireframe.

To summarize: The top-level “Language & Text” screen should have page
stack items for “On-screen keyboard” and “Hardware keyboard”. Both of
those screens should start with a “Keyboard layouts” page stack item.
The “On-screen keyboard” screen should follow this with a
“Transparency:” slider, with ends labelled “None” and “High”.

When, and only when, you are interacting with this slider, the OSK
should appear so that you can see the effect in real time.

** Attachment added: "wirefame"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1647603/+attachment/4809327/+files/keyboard-onscreen.narrow.png

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

Title:
  Add option for semi-transparent keyboard

Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

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

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

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

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

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


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

2017-01-26 Thread Matthew Paul Thomas
The design has not been changed yet.

** Project changed: ubuntu-ux => ubuntu-system-settings (Ubuntu)

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

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: Femma (femma) => Matthew Paul Thomas (mpt)

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

Title:
  Add option for semi-transparent keyboard

Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

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

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

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

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

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


[Touch-packages] [Bug 1521518] Re: No way to invoke OSK when a hardware keyboard is connected

2017-01-26 Thread Matthew Paul Thomas
(The spec change I proposed a year ago has since been approved.)

** Changed in: ubuntu-ux
   Status: In Progress => Fix Committed

** Changed in: ubuntu-ux
 Assignee: Femma (femma) => Matthew Paul Thomas (mpt)

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

Title:
  No way to invoke OSK when a hardware keyboard is connected

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  Incomplete
Status in ubuntu-keyboard:
  New
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  There are mice on the market that claim to be keyboards as well. This
  inhibits OSK. We can try and find out how many keys they have and be
  smart about it.

  Regardless, we should have a way of forcing the OSK, especially on
  touch-enabled devices. Whether it's triggered by a touch (as opposed
  to mouse click) on the text area, or with a button in the text field
  (replaced with the clear icon when you start typing). Another option
  is the copy/paste dropdown.

  <https://goo.gl/CJ1YLB>:
  
  The on-screen keyboard should appear if:
  * no external keyboard is connected, and a text field becomes focused; or
  * an external keyboard is connected, but the most recent text typed anywhere 
was with the OSK, and a text field becomes focused; or
  * an external keyboard is connected, and the most recent text typed was with 
an external keyboard, but you tap in the already-focused text field. (App 
developers are responsible for emulating this behavior in typable areas that 
are not text fields.)
  

  == original description ==

  1. Boot nexus 7
  2. In the login screen, test that OSK works by tapping the password textfield
  3. swipe keyboard back down after testing it works
  4. Turn on Bluetooth mouse to get a mouse cursor
  5. Click on password textfield

  OSK doesn't pop up, touch tapping on the field doesn't bring up the
  OSK anymore either.

  ie. The login screen is not usable with mouse connected - cannot type
  in password via OSK since it doesn't come up when clicking the
  password textfield with mouse.

  See attached screenshot. Focus on textfield. Would expect OSK to show
  up.

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

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


[Touch-packages] [Bug 1566172] Re: [SUGGESTION] Use the space bar for moving the text cursor

2017-01-26 Thread Matthew Paul Thomas
Specification updated. 

** Changed in: ubuntu-ux
   Status: New => Fix Committed

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

Title:
  [SUGGESTION] Use the space bar for moving the text cursor

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

Bug description:
  I have an idea which maybe considered to be implemented.
  What if we use the space bar for moving the text cursor horizontally or even 
vertically.
  Currently, moving the cursor is quite hard and inaccurate.
  Space bar is quite big and makes it a good place to swipe to move the cursor.
  With this approach, we're not using more space and instead use a big part of 
the keyboard that is only there mostly for inserting spaces. The sensitivity is 
critical though because you don't want unintended movement of the cursor but I 
think it's very much doable.

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

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


[Touch-packages] [Bug 1650022] Re: We need a "close" action for killing an app in a trust prompt

2017-01-19 Thread Matthew Paul Thomas
I’ve explained what I understand by “original designs”. So, which
designs are you referring to? Can you point me to a design document, or
a mockup, or anything? I’m happy to work on this, but I can’t change the
design of something I can’t locate.

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

Title:
  We need a "close" action for killing an app in a trust prompt

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The original designs for trust prompts included a close action in the
  header to close apps that were opened in a trust session.  This is
  particularly important when apps might not behave well or hang, there
  is no way out.  The close action is like a back button to take you
  back out of the app.

  We're close to landing trust session support in content-hub, where
  we'll open source apps for content picking in a trust prompt.  We've
  found apps that have a tendency to hang, leaving the user no way out
  besides killing both the source and destination apps.  Clearly those
  apps need some fixing, but we need to give the user an easy way out.

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

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


[Touch-packages] [Bug 1650022] Re: We need a "close" action for killing an app in a trust prompt

2017-01-16 Thread Matthew Paul Thomas
The same applies for non-hang misbehavior: the method of force-closing
an app should be exactly the same regardless of whether a trust prompt
is open or not.

However, I’m sorry I should have read the report more closely and
noticed the phrase “content picking in a trust prompt”. To me, trust
prompts and the content picker are very different things, so I don’t
understand this phrase. I designed trust prompts, but I have never come
across any design document from anyone covering the content picker
(there are none on the design site).

So, what do you mean by “app B does not give you a way to go back”? Why
is the ability to exit the content picker under the control of app B at
all? For example, the macOS Open file dialog lets you browse the
libraries of iTunes, iPhoto, and Photos, but you aren’t “in” those apps
and they don’t get to control the dialog’s Cancel button.

** Changed in: ubuntu-ux
   Status: Invalid => Incomplete

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

Title:
  We need a "close" action for killing an app in a trust prompt

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The original designs for trust prompts included a close action in the
  header to close apps that were opened in a trust session.  This is
  particularly important when apps might not behave well or hang, there
  is no way out.  The close action is like a back button to take you
  back out of the app.

  We're close to landing trust session support in content-hub, where
  we'll open source apps for content picking in a trust prompt.  We've
  found apps that have a tendency to hang, leaving the user no way out
  besides killing both the source and destination apps.  Clearly those
  apps need some fixing, but we need to give the user an easy way out.

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

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


[Touch-packages] [Bug 1650022] Re: We need a "close" action for killing an app in a trust prompt

2017-01-10 Thread Matthew Paul Thomas
As far as I know, “the original designs for trust prompts” are what I
specified in July 2013.

They have never — then or since — included a header at all, let alone a
close button.

This is because a close button for a dialog is an anti-pattern: it has
ambiguous effect, and it makes it less obvious that the window is a
dialog at all. That is also why, if “a server-side decorated [dialog
has] its own close button in the title bar”, that is a bug in Mir: per
spec, no dialogs ever should. 

Now, an app might misbehave or hang when a trust prompt is open. But
most of the time when an app misbehaves or hangs, a trust prompt is not
open — simply because a trust prompt is not open the vast majority of
the time that any app is running! So having a different method for
force-closing the app, when a trust prompt happens to be open, would
increase cognitive load for no obvious reason. The method of force-
closing an app should be — and is — exactly the same regardless of
whether a trust prompt is open or not.

But while content hub transfers will be only a small minority of the
cases of an app hanging, an app hanging is a common case — arguably the
majority legitimate case — for wanting to force-close an app. So it
would be reasonable to have a prompt inviting you to force-close an app
whenever it’s hung for any reason, whether the hang involves any trust
prompt or not. This would be equivalent to the “The app {Name of App}
has stopped responding” dialog I specified for apport.


Separately, if either content-hub source or destination apps hanging
causes the other to hang too, that’s probably a bug in content-hub. One
possible solution would be to cancel the transfer if nothing has
happened after a given period. Perhaps there are other solutions.

I’m marking this as Invalid because those two issues would be tackled
independently, while the change assumed in this report should not be
implemented at all.

** Changed in: ubuntu-ux
   Status: New => Invalid

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

Title:
  We need a "close" action for killing an app in a trust prompt

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

Bug description:
  The original designs for trust prompts included a close action in the
  header to close apps that were opened in a trust session.  This is
  particularly important when apps might not behave well or hang, there
  is no way out.  The close action is like a back button to take you
  back out of the app.

  We're close to landing trust session support in content-hub, where
  we'll open source apps for content picking in a trust prompt.  We've
  found apps that have a tendency to hang, leaving the user no way out
  besides killing both the source and destination apps.  Clearly those
  apps need some fixing, but we need to give the user an easy way out.

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

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


[Touch-packages] [Bug 1482551] Re: "External" app setting -> System Settings -> Back doesn't return to "External" app

2016-12-20 Thread Matthew Paul Thomas
*** This bug is a duplicate of bug 1447601 ***
https://bugs.launchpad.net/bugs/1447601

Rodney’s right that “Back” shouldn’t reopen an indicator menu. But it
shouldn’t exit System Settings either. This is because, as Rodney says,
that shouldn’t happen if System Settings was already running. But people
can’t be expected to know *whether* System Settings is already running,
especially on devices where background apps don’t have any screen
representation, and especially on devices where the OS can shut down a
background app at any time. Therefore, it shouldn’t happen at all.

I specified different behavior for Back: “…the behavior of the Back
button should be: … if you came to the current screen any other way (for
example from a “deep link” in a different app), it should navigate to
the screen you were most recently on.”


Anyway, the supposed “steps to reproduce” do not match the original bug
report, which is specifically about the phone settings. This report is
now causing enough confusion that I think it’s more confusing than
useful to keep it open separately from bug 1447601.

** Summary changed:

- "External" app setting -> System Settings -> Back doesn't return to 
"External" app
+ Phone app -> Settings -> Back doesn't return to Phone app

** Description changed:

  From settings in telephony suite, when tap return button, it goes back
  to system settings instead of phone/one of the telephony suite
- 
- Steps to reproduce:
- 1. Open Ubuntu Clock Application
- 2. Click Gear button on top right corner
- 3. Click "Change time and date"
- 4. "Time & Date" System settings is revealed
- 
- Current
- 4. On top left corner, the "Back" button is displayed. Pressing it return to 
General System settings.
- 
- Expected:
- 4. On top left corner, the "Close" button is displayed. Pressing it close 
system-settings application and return to Ubuntu-Clock-Application.
- 
- Proposal:
- When the ubuntu-system-settings application is executed from external 
application, then instead of "Back" button, System-settings should display 
"Close" button.

** This bug has been marked a duplicate of bug 1447601
   "Phone" app settings are oddly in System Settings

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

Title:
  Phone app -> Settings -> Back doesn't return to Phone app

Status in Ubuntu Clock App:
  New
Status in Ubuntu UX:
  Triaged
Status in dialer-app package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  From settings in telephony suite, when tap return button, it goes back
  to system settings instead of phone/one of the telephony suite

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

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


[Touch-packages] [Bug 1637100] Re: Default hotspot SSID name should be customized per device

2016-10-27 Thread Matthew Paul Thomas
: “The dialog should be pre-
filled with: ‘Choose a name:’ defaulting to the device name, and no
password”

Setting a custom device name is bug 1427106. My wireframe implies that
by default it should be “{Person Name}’s Phone”. But that wouldn’t work
for non-phone devices, so perhaps it should be “{Person Name}’s {Model
Name}” (which would also work better if someone had multiple phones).

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

Title:
  Default hotspot SSID name should be customized per device

Status in indicator-network package in Ubuntu:
  New

Bug description:
  Hotspot SSID name should be customized per device and not always use
  "Ubuntu" as default. The reason is that APs with the same name and
  authentication method are considered by the WiFi standards to belong
  to the same network.

  This makes that when we have two Ubuntu phones with hotspot activated,
  clients try to roam between them. Having an unique identifier should
  be easy to do, maybe by mangling some MAC bytes.

  See related comments 11 and 12 in bug LP: #1478319.

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

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


[Touch-packages] [Bug 1521518] Re: No way to invoke OSK when a hardware keyboard is connected

2016-10-24 Thread Matthew Paul Thomas
W.r.t. “SDK might need adapting”, yes, this is largely a toolkit bug,
because a toolkit is the most practical component to keep track of when
“a text field becomes focused”. You can’t expect every app author to do
this themselves, and you can’t expect users to learn+remember any
alternative way of invoking the OSK.

An example flow would be:
a. You tap in a text field.
b. The toolkit says to the shell, “hey, I just focused a text field”.
c. The shell checks whether an external keyboard is connected; it is.
d. The shell checks whether the last character typed anywhere was with the OSK; 
it was.
e. The shell therefore opens the OSK, and tells the toolkit that it’s done so…

(…The shell also tells the toolkit what part of the window, if any, the
OSK is obscuring. Then the toolkit says, “oh dear, that’s over top of
the text field”, and scrolls the view to keep the field visible. But
that’s another story.)

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

Title:
  No way to invoke OSK when a hardware keyboard is connected

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  Incomplete
Status in ubuntu-keyboard:
  New
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  There are mice on the market that claim to be keyboards as well. This
  inhibits OSK. We can try and find out how many keys they have and be
  smart about it.

  Regardless, we should have a way of forcing the OSK, especially on
  touch-enabled devices. Whether it's triggered by a touch (as opposed
  to mouse click) on the text area, or with a button in the text field
  (replaced with the clear icon when you start typing). Another option
  is the copy/paste dropdown.

  :
  
  The on-screen keyboard should appear if:
  * no external keyboard is connected, and a text field becomes focused; or
  * an external keyboard is connected, but the most recent text typed anywhere 
was with the OSK, and a text field becomes focused; or
  * an external keyboard is connected, and the most recent text typed was with 
an external keyboard, but you tap in the already-focused text field. (App 
developers are responsible for emulating this behavior in typable areas that 
are not text fields.)
  

  == original description ==

  1. Boot nexus 7
  2. In the login screen, test that OSK works by tapping the password textfield
  3. swipe keyboard back down after testing it works
  4. Turn on Bluetooth mouse to get a mouse cursor
  5. Click on password textfield

  OSK doesn't pop up, touch tapping on the field doesn't bring up the
  OSK anymore either.

  ie. The login screen is not usable with mouse connected - cannot type
  in password via OSK since it doesn't come up when clicking the
  password textfield with mouse.

  See attached screenshot. Focus on textfield. Would expect OSK to show
  up.

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

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


[Touch-packages] [Bug 1628649] Re: Date and time are too far away from each other

2016-09-29 Thread Matthew Paul Thomas
** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  Date and time are too far away from each other

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  In Yakkety beta the date and time were moved farther away from each
  other than before.

  There's now an about 15px space between them on my machine, whereas
  the gap between all other symbols is usually 12px.

  Date and time are the two pieces of information that are logically the
  closest to each other, hence having a larger space between them than
  between irrelevant icons is really disturbing to my eyes.

  I understand that it deserves a bigger space than a simple space
  character (as between the day of week, month and day), but it
  shouldn't be bigger than the gap between let's say wifi strenght and
  kbd layout, or between the time and the poweroff symbol etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 28 20:56:44 2016
  InstallationDate: Installed on 2012-05-30 (1582 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-09-23 (5 days ago)

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

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


[Touch-packages] [Bug 1623046] Re: text doesn't fit the button field in low battery notification(spanish)

2016-09-14 Thread Matthew Paul Thomas
If I understood Christian Dwyan correctly, he says that this is not a
duplicate of bug 1580974 because Unity is not using standard toolkit
buttons in notifications.

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

Title:
  text doesn't fit the button field in low battery notification(spanish)

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

Bug description:
  Enviroment:

  current build number: 187
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-09-13 10:09:37
  version version: 187
  version ubuntu: 20160913
  version device: 20160809.0
  version custom: 20160831--42-26-vivid

  Preconditions:  > 15% battery life

  Steps to reproduce:

  1º When battery < 15% you can trigger low battery notification by plug/unplug 
charger
  2º When in Spanish language, check the left button doesn't fit the 
screen(battery settings)

  Current result: Left button of low battery notification is bigger than
  button field

  Expected result: Text should be inside the button field

  Add info: not sure if it happens also in krillin as mine is fully
  charged right now

   (Canonical-only link): “In the unlikely event
  that a button’s label is too long for its maximum possible width, it
  should be ellipsized in the middle, and a warning should be logged for
  the developer’s attention.”

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

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


[Touch-packages] [Bug 1580974] Re: Button label should ellipsize in the middle

2016-09-14 Thread Matthew Paul Thomas
I also specified middle ellipsis for radio menu menubuttons.
 (Canonical-only link, sorry)

In future I would expect it to be specified for dropdown menu
menubuttons, for menu items in general, for headers, and for list items.
(From a quick survey, none of those specify overflow behavior
currently.)

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

Title:
  Button label should ellipsize in the middle

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

Bug description:
  As per the Buttons spec

  "In the unlikely event that a button’s label is too long for the width
  available, it should be ellipsized in the middle"

  Currently the Label in ButtonForeground ellipsizes in the end.

  Also quoting Matthew on the reasoning:

  (1 Two buttons with long but similar labels are more likely to differ at 
their ends than their middles (e.g. “Change This Event Only” vs. “Change This 
And Future Events”).
  (2 End ellipsis is already used to mean “you’ll need to do something else 
after tapping this”.

   (Canonical-only link, sorry): “In the unlikely
  event that a button’s label is too long for its maximum possible
  width, it should be ellipsized in the middle (because the start and
  end are more likely to be distinct between buttons), and a warning
  should be logged for the developer’s attention.”

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

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


[Touch-packages] [Bug 1580974] Re: Button label should ellipsize in the middle

2016-09-14 Thread Matthew Paul Thomas
** Description changed:

  As per the Buttons spec
  
  "In the unlikely event that a button’s label is too long for the width
  available, it should be ellipsized in the middle"
  
  Currently the Label in ButtonForeground ellipsizes in the end.
  
  Also quoting Matthew on the reasoning:
  
  (1 Two buttons with long but similar labels are more likely to differ at 
their ends than their middles (e.g. “Change This Event Only” vs. “Change This 
And Future Events”).
  (2 End ellipsis is already used to mean “you’ll need to do something else 
after tapping this”.
+ 
+  (Canonical-only link, sorry): “In the unlikely
+ event that a button’s label is too long for its maximum possible width,
+ it should be ellipsized in the middle (because the start and end are
+ more likely to be distinct between buttons), and a warning should be
+ logged for the developer’s attention.”

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Button label should ellipsize in the middle

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

Bug description:
  As per the Buttons spec

  "In the unlikely event that a button’s label is too long for the width
  available, it should be ellipsized in the middle"

  Currently the Label in ButtonForeground ellipsizes in the end.

  Also quoting Matthew on the reasoning:

  (1 Two buttons with long but similar labels are more likely to differ at 
their ends than their middles (e.g. “Change This Event Only” vs. “Change This 
And Future Events”).
  (2 End ellipsis is already used to mean “you’ll need to do something else 
after tapping this”.

   (Canonical-only link, sorry): “In the unlikely
  event that a button’s label is too long for its maximum possible
  width, it should be ellipsized in the middle (because the start and
  end are more likely to be distinct between buttons), and a warning
  should be logged for the developer’s attention.”

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

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


[Touch-packages] [Bug 1623046] Re: text doesn't fit the button field in low battery notification(spanish)

2016-09-13 Thread Matthew Paul Thomas
** Package changed: indicator-power (Ubuntu) => ubuntu-ui-toolkit
(Ubuntu)

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

** Description changed:

  Enviroment:
  
  current build number: 187
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-09-13 10:09:37
  version version: 187
  version ubuntu: 20160913
  version device: 20160809.0
  version custom: 20160831--42-26-vivid
  
  Preconditions:  > 15% battery life
  
  Steps to reproduce:
  
  1º When battery < 15% you can trigger low battery notification by plug/unplug 
charger
  2º When in Spanish language, check the left button doesn't fit the 
screen(battery settings)
  
  Current result: Left button of low battery notification is bigger than
  button field
  
  Expected result: Text should be inside the button field
  
  Add info: not sure if it happens also in krillin as mine is fully
  charged right now
+ 
+  (Canonical-only link): “In the unlikely event
+ that a button’s label is too long for its maximum possible width, it
+ should be ellipsized in the middle, and a warning should be logged for
+ the developer’s attention.”

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

Title:
  text doesn't fit the button field in low battery notification(spanish)

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

Bug description:
  Enviroment:

  current build number: 187
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-09-13 10:09:37
  version version: 187
  version ubuntu: 20160913
  version device: 20160809.0
  version custom: 20160831--42-26-vivid

  Preconditions:  > 15% battery life

  Steps to reproduce:

  1º When battery < 15% you can trigger low battery notification by plug/unplug 
charger
  2º When in Spanish language, check the left button doesn't fit the 
screen(battery settings)

  Current result: Left button of low battery notification is bigger than
  button field

  Expected result: Text should be inside the button field

  Add info: not sure if it happens also in krillin as mine is fully
  charged right now

   (Canonical-only link): “In the unlikely event
  that a button’s label is too long for its maximum possible width, it
  should be ellipsized in the middle, and a warning should be logged for
  the developer’s attention.”

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

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


[Touch-packages] [Bug 1276066] Re: Checkbox needs 'unknown' state

2016-09-09 Thread Matthew Paul Thomas
For the reasons given above, I have not included an “animated” property
or an “unknown” state in the toolkit specification for checkboxes.
 (Canonical-only link, sorry) As with any control,
it’s generally better not to show a checkbox until you know what its
value is supposed to be.

** Changed in: ubuntu-ux
   Status: Triaged => 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/1276066

Title:
  Checkbox needs 'unknown' state

Status in Ubuntu UI Toolkit:
  Incomplete
Status in Ubuntu UX:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  The Checkbox component always animates its state transitions.
  Sometimes, the "checked" property is set shortly after initialization,
  which shows the animation when creating a page. For example, this
  happens when using the GSettings object, which fills in its properties
  in its componentCompleted:

  GSettings {
  id: settings
  schema.id: "com.ubuntu.touch.system"
  }

  CheckBox {
  checked: settings.autoBrightness
  }

  It would be nice if there was a property "animate" which could be used
  to suppress animations while loading a page.

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

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


[Touch-packages] [Bug 1541588] Re: [System Settings] Changes needed for the UI on a tablet device

2016-09-09 Thread Matthew Paul Thomas
** Changed in: ubuntu-ux
   Status: Triaged => In Progress

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

Title:
  [System Settings] Changes needed for the UI on a tablet device

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  In Progress
Status in indicator-network package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  Note for design: can we simply avoid referring to the/this phone as in
  most uses its not necessary for clarity, and then the same text can
  always apply..

  Main panel:
  Hide Cellular
  Hide Hotspot
  Hide Phone
  About this phone -> About this device or just About
  Reset phone -> Reset device or just Reset

  Background
  Ensure default for images is landscape

  Sound:
  Hide Ringer, Phone Calls and Messages sections

  Security and Privacy
  Hide SIM PIN
  Locking and unlocking > Lock security "Unlock the phone using" --> "Unlock 
the device using"
  Locking and unlocking > Lock when idle  "Lock the phone when..." --> "Lock 
the device when ..."
  "Phone won't lock..." --> Device won't lock ..."

  About this device
  Hide IMEI
  Developer mode >  "this phone" --> "this device"

  A minor point but what happens when we search in settings for hidden
  stuff

  
  
  Note from design:

  - The text in the UI should never refer to "Phone", "Tablet" or
  "Desktop".  Instead the word "Device" should be used.

  - e.g. "About This Computer" or "About This Phone" is incorrect. This
  wording should be changed to "About this device" in both the indicator
  and System Settings to be convergence friendly.

  - This change applies to all device references in the UI.

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

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


[Touch-packages] [Bug 1513435] Re: [online-accounts] No edit UI

2016-09-08 Thread Matthew Paul Thomas
Online Accounts is for remembering, updating, and reusing account
credentials. It is not for remembering, or providing UI to edit, app-
specific settings like mail server address and port number. That is up
to individual apps. There are three reasons for this:

(1) Putting app-specific settings in Online Accounts would complicate
the Online Accounts UI with settings for apps that you may never use.
For example, if you use a Yahoo account for Yahoo Mail, not Yahoo
Calendar, calendar-specific settings in Online Accounts would be
distracting. (And time-wasting, if you got the impression that you had
to configure some of them anyway.)

(2) Apps for services that have non-UOA providers have to provide UI for
those app-specific settings anyway. For example, Dekko has its own UI
for editing server address, port number etc for non-UOA IMAP accounts,
and it would need that UI even if UOA had its own UI for those same
settings for UOA providers. So if it did, you’d end up with UI for the
same settings in different places, with different layout and
terminology, depending on the type of account.

(3) If a provider starts, stops, or changes a particular service, an app
can be updated more quickly than the OS can. For example, if tomorrow
Facebook started providing an e-mail service, or Yahoo stopped providing
their e-mail service — or if “an e-mail provider might force SSL, or
change the address of its imap server” — then Dekko could update within
days, without having to wait for an update to Ubuntu that might take
weeks. Similarly, if Google released a new video calling app, that app
could use UOA without having to wait for Ubuntu to update UOA to “know”
that Google accounts can be used for video calling. All UOA ever needs
to know is how to sign in to an account, and which apps have permission
to use it, not what they are using it for.

** Changed in: ubuntu-ux
   Status: Triaged => Won't Fix

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

Title:
  [online-accounts] No edit UI

Status in Ubuntu UX:
  Won't Fix
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  Currently there is no way to edit an accounts credentials and other
  settings stored in an online account.

  This is needed for apps like Dekko that will store a lot of editable
  details such as server addresses, port numbers etc. These should be
  easily editable after account creation and not have to delete and re-
  create an account just to adjust one value.

  As an example, a server or corporate policy might be in place that you
  have to change your password every 90 days. This will be inconvenient
  to the user to have to re-create the account and also lose any
  additional (possibly critical) data stored in an app that is bound to
  that account.

  --

  Questions to Design team:
  1) is it OK to let account providers add more content to that page?
  2) if yes, where should this content appear?

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

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


[Touch-packages] [Bug 1603175] Re: No resolution configuration available

2016-09-06 Thread Matthew Paul Thomas
** Description changed:

  In my desktop unity8 is clearly in the wrong resolution:
-  - the font in the titlebar is quite pixelated
-  - the cursor is huge
+  - the font in the titlebar is quite pixelated
+  - the cursor is huge
  
  It would be required to have a setting like the one in unity7 to set the
  correct resolution of the screen.
+ 
+ : “
+ ‘Resolution:’ radio menu should have options for each available
+ resolution for the display…”

** Changed in: ubuntu-ux
   Status: New => Fix Committed

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  No resolution configuration available

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  In my desktop unity8 is clearly in the wrong resolution:
   - the font in the titlebar is quite pixelated
   - the cursor is huge

  It would be required to have a setting like the one in unity7 to set
  the correct resolution of the screen.

  : “
  ‘Resolution:’ radio menu should have options for each available
  resolution for the display…”

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

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


[Touch-packages] [Bug 1535335] Re: [App permissions] Change prompt "wants to record audio" to "wants to access microphone"

2016-09-06 Thread Matthew Paul Thomas
This is not a design bug: the design already specifies that the text is
supposed to be “wants to use the microphone”.


** No longer affects: ubuntu-ux

** Summary changed:

- [App permissions] Change prompt "wants to record audio" to "wants to access 
microphone"
+ [App permissions] Change prompt "wants to record audio" to "wants to use the 
microphone"

** Description changed:

  The prompt when the camera wants to access the hardware to record audio
  is currently "wants to record audio". This is not really accurate since
  an app can request access to the microphone without actually recording
  anything. furthermore the direct translation to French as an example is
  not really meaningful.
  
- 
- Something like "wants to access the microphone." would be more accurate since 
it's actually what the application requests access to.
- 
  "Microphone" is also consistent with the word used in system-
  settings/security & privacy/app permissions
+ 
+ : “Prompt text
+ … wants to use the microphone”

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Triaged

** Tags added: string-fix

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

Title:
  [App permissions] Change prompt "wants to record audio" to "wants to
  use the microphone"

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  The prompt when the camera wants to access the hardware to record
  audio is currently "wants to record audio". This is not really
  accurate since an app can request access to the microphone without
  actually recording anything. furthermore the direct translation to
  French as an example is not really meaningful.

  "Microphone" is also consistent with the word used in system-
  settings/security & privacy/app permissions

  : “Prompt
  text … wants to use the microphone”

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

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


[Touch-packages] [Bug 1386579] Re: [SDK] Toolkit lacks radio buttons

2016-09-04 Thread Matthew Paul Thomas
** Description changed:

  Currently the toolkit has no radio buttons.
  
  As a result, developers are using checkboxes for groups of options where only 
one can be selected at a time.
  
  
  This is misleading. Everywhere else, checking a checkbox toggles its
  state, whereas here special code is used to ensure it remains checked.
  And on every other platform, checking a checkbox doesn't uncheck another
  checkbox.
  
- : "Radio buttons are one of the three types of
+ : “Radio buttons are one of the three types of
  radio control (along with the radio list and the radio menu), letting
- you choose exactly one from a group of options..."
+ you choose exactly one from a group of options…”

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Pierre Bertet (bpierre)

** No longer affects: ubuntu-ux

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

Title:
  [SDK] Toolkit lacks radio buttons

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

Bug description:
  Currently the toolkit has no radio buttons.

  As a result, developers are using checkboxes for groups of options where only 
one can be selected at a time.
  

  This is misleading. Everywhere else, checking a checkbox toggles its
  state, whereas here special code is used to ensure it remains checked.
  And on every other platform, checking a checkbox doesn't uncheck
  another checkbox.

  : “Radio buttons are one of the three types of
  radio control (along with the radio list and the radio menu), letting
  you choose exactly one from a group of options…”

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

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


[Touch-packages] [Bug 1370008] Re: URL Dispatcher Should Prompt on Bad URL

2016-09-04 Thread Matthew Paul Thomas
** Changed in: url-dispatcher (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

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

Title:
  URL Dispatcher Should Prompt on Bad URL

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in url-dispatcher package in Ubuntu:
  Confirmed

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

  : "Whenever
  the URL dispatcher is called on to open an address of a protocol that
  it does not understand (url-dispatcher-bad-url), it should open an
  alert with the title “Unrecognized Address”, text of the form ‘Ubuntu
  can’t open addresses of type “{protocol:}”.’, and an “OK” button. To
  prevent denial of UI service, however, the alert should not open if it
  has already opened more than three times in the past minute."

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

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


[Touch-packages] [Bug 1607182] Re: Month calendar in the datetime pull-down makes it longer than krillin's screen

2016-08-01 Thread Matthew Paul Thomas
This is one of the reasons that I omitted the calendar from the phone
menu design in the first place. (The other reason is that on a phone, a
calendar in a full-screen menu has little benefit compared to just
switching to the calendar app; both completely cover whatever other app
you’re using.)

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

Title:
  Month calendar in the datetime pull-down makes it longer than
  krillin's screen

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

Bug description:
  Month calendar in the datetime pull-down makes it longer than
  krillin's screen.

  You have to scroll it once opened, which is less than ideal.

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

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


[Touch-packages] [Bug 1333228] Re: [sdk] Clicking on checkbox label should toggle the checkbox

2016-07-28 Thread Matthew Paul Thomas
This is now part of the toolkit specification for checkboxes.

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

** Description changed:

  For instance, take the "Connec to " pop-up dialog. When I touch 
the:
  [   ] Show password
  checkbox *label*, I'd expect the checkbox to toggle. I shouldn't need to have 
to exactly touch the checkbox box, which is a small area.
+ 
+  (currently Canonical-only link): “As with a
+ switch or radio button, when a checkbox has a label, it should be
+ clickable/tappable together with the checkbox itself.”

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

Title:
  [sdk] Clicking on checkbox label should toggle the checkbox

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  For instance, take the "Connec to " pop-up dialog. When I touch 
the:
  [   ] Show password
  checkbox *label*, I'd expect the checkbox to toggle. I shouldn't need to have 
to exactly touch the checkbox box, which is a small area.

   (currently Canonical-only link): “As with a
  switch or radio button, when a checkbox has a label, it should be
  clickable/tappable together with the checkbox itself.”

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

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


[Touch-packages] [Bug 1604705] Re: Don't scare users who want to use propose

2016-07-26 Thread Matthew Paul Thomas
The current text is quite confused. (“Proposed updates are only for
testing updates”? No. They aren’t *for* testing updates, they *are*
updates.) And its lack of wrapping single-handedly makes the whole
window much wider than it should be. So there’s a lot of room for
improvement.

However, it’s strange to acknowledge that “enabling proposed can make
the system unstable” but then immediately to claim that we should “not
discourage [people from] using it”. Of course we should discourage
people from making their system unstable! If there was no reason to
discourage -proposed, there would be no reason not to have it on by
default, which would be tantamount to it not existing at all.

Now, there are subtler and cruder methods of discouragement. Putting it
in a “Developer Options” tab is by itself a subtle discouragement: “I’m
not a developer, maybe I should stay away”. My current design goes
further, putting it in a “Contributor Console” that’s a separate utility
altogether. 

As long as that app remains unimplemented, I would use the same text as I 
specified there:
Check for updates being tested (-proposed)
And replace the label above with a caption underneath, something like:
Use proposed updates if you’re willing to report bugs on any problems that 
occur.

** Changed in: software-properties (Ubuntu)
   Status: New => Triaged

** Summary changed:

- Don't scare users who want to use propose
+ Don't scare users who want to use -proposed

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

Title:
  Don't scare users who want to use -proposed

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  The GUI is intended for use by normal user and enabling proposed can
  make the system unstable. Despite this, some users want to use early
  release of packages and the current message discourage them of doing
  so.

  It should be reworded to explain clearly that this channel contains
  early release of packages and not discourage them of using it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.1
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 20 09:43:11 2016
  InstallationDate: Installed on 2013-09-03 (1050 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1501714] Re: [address book] search field without clicking on the bouton

2016-07-25 Thread Matthew Paul Thomas
Tapping the Search button both reveals *and* focuses the search field.
So if you are starting a search from scratch, the number of clicks/taps
needed is exactly the same for the button as it would be for an always-
visible field: one.

An always-visible search field would, though, be better for:
* reassuring you that the current view is the full list, not search results;
* doing other things in the header while using a search (bug 1606243).

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

Title:
  [address book] search field without clicking on the bouton

Status in Ubuntu UX:
  Triaged
Status in address-book-app package in Ubuntu:
  Incomplete

Bug description:
  When I am in my contact app, and I need to search someone, I need to
  click on the icon "serach" first. Why is that? I think it would be
  better if the field was already accessible. When you search a contact
  from the phone app, it is anoying to have to clik on another button.

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

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


[Touch-packages] [Bug 1606243] [NEW] Search malfunctions after selecting a search result

2016-07-25 Thread Matthew Paul Thomas
Public bug reported:

Ubuntu 15.04 (r385)

Contacts:
0. Set up at least two contacts.
1. Tap the search button in the header.
2. Search for something that’s present in at least one contact.
3. Long-tap one of the search results.
What happens:
3. The search field disappears from the header, and the search is cancelled.

Dekko:
0. Receive at least two messages.
1. Tap the search button in the header.
2. Search for something that’s present in at least one message.
3. Long-tap one of the search results.
4. Tap Back.
5. Tap Search.
What happens:
3. The search field disappears from the header, but the search is not cancelled.
4. The header returns to its usual state, but you are still viewing only the 
search results.
5. The folder returns to its usual contents.

What should happen:
3. App behavior when you select a search result should be consistent.
4. A full listing, and search results, should be clearly distinct.

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

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

** Also affects: dekko (Ubuntu)
   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/1606243

Title:
  Search malfunctions after selecting a search result

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

Bug description:
  Ubuntu 15.04 (r385)

  Contacts:
  0. Set up at least two contacts.
  1. Tap the search button in the header.
  2. Search for something that’s present in at least one contact.
  3. Long-tap one of the search results.
  What happens:
  3. The search field disappears from the header, and the search is cancelled.

  Dekko:
  0. Receive at least two messages.
  1. Tap the search button in the header.
  2. Search for something that’s present in at least one message.
  3. Long-tap one of the search results.
  4. Tap Back.
  5. Tap Search.
  What happens:
  3. The search field disappears from the header, but the search is not 
cancelled.
  4. The header returns to its usual state, but you are still viewing only the 
search results.
  5. The folder returns to its usual contents.

  What should happen:
  3. App behavior when you select a search result should be consistent.
  4. A full listing, and search results, should be clearly distinct.

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

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


[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements

2016-07-22 Thread Matthew Paul Thomas
Saying that the update “may take several minutes” is, I think, probably
not an effective solution to the problem of people powering off the
phone because it looks like it’s stuck. It doesn’t matter how long they
expect it to take: if nothing on the screen is changing, it would still
look like it’s stuck.

I don’t know why Plymouth can show changing text but the Ubuntu Touch
startup screen can’t, but if that will continue to be the case, I guess
fixing bug 1385410 is the only way to provide the necessary reassurance.

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

Title:
  AppArmor policy compile improvements

Status in AppArmor:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  Triaged
Status in click-apparmor package in Ubuntu:
  Triaged

Bug description:
  apparmor_parser can take a long time to compile policy especially when there 
is a lot of policy, so we want to utilize compiled cache profile as much as 
possible. Cache files will have to be regenerated in the following cases:
   * the kernel .features file is updated (eg, new features are added to
     apparmor in the new kernel)
   * apparmor itself is updated
   * on devices with click packages, apparmor-easyprof-ubuntu and/or
     click-apparmor is updated

  As of 2014-10-02, what can be expected is:

  - Systems with system-image updates (eg, Ubuntu Touch):
    - First boot will use the precompiled cache files in the rootfs or custom
  tarball and be fast
    - Reboots will use the cache files on the device and be fast
    - First boots after upgrades will use the cache files on the device if the
  above conditions are not met and be fast
    - Production devices will not meet any of those conditions except under
  exceptional and rare circumstances (eg, major OS upgrades like 14.10 to
  15.04) and be fast
    - First boots after upgrades that meet one of the conditions will need to
  regenerate the cache. This can happen on development releases where the
  kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates
  - Systems with apt updates (eg, current Ubuntu Desktop and Server):
    - First boot will compile cache files
    - Reboots will use the cache files on the machine and be fast
    - First boots after upgrades will use the cache files on the machine if the
  above conditions are not met and be fast
    - Stable releases of Ubuntu will not meet any of those conditions except
  under exceptional and rare circumstances (eg, major OS upgrades like
  14.10 to 15.04) and be fast
    - First boots after upgrades that meet one of the above conditions will
  need to regenerate the cache. This can happen on development releases
  where the kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates

  In addition to the above, updates to only apparmor-easyprof-ubuntu
  will regenerate the cache files for only the policy that is affected
  (eg, if there is a change to the location policy group in policy
  version 1.2, only apps using this policy version and this policy group
  will need to be recompiled).

  Planned improvements (in order of most likely to be done first):
  1. Finetuning the checks to invalidate the cache (eg, .md5sums could only
     be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an
     md5sum on apparmor_parser since it could change the cache and the md5sum
     will always change. Furthermore, apparmor-easyprof-ubuntu is all policy
     so there is no gain there. click-apparmor could possibly benefit, but
     it doesn't change often and when it does, it is typically for policy)
  2. Investigate ways to utilize the custom tarball and rootfs precompiled
     cache files on upgrades when apparmor, apparmor-easyprof-ubuntu and
     click-apparmor are updated: DONE
  3. Improve cache handling for app store apps (eg, having the app store
     server precompile them so that the device can download them when it
     needs to rather than having to regenerate them itself): WONTFIX
     (doesn't scale)
  4. For systems with apt upgrades, compile the policy either during
     install or on kernel upgrade rather than on boot. For systems with
     read-only fs-style upgrades, compile the policy prior to reboot
     rather than on boot.
  5. Support cache files per kernel .features file (or kernel version).
     This will allow people to boot into a previous kernel without having
     to recompile policy
  6. Improve parser compile time
  7. Investigate how to utilize profile composition and profile stacking to
     decrease compile and load times (eg, one idea is that the policy template
     is compiled once and each policy group once such that the parser 

[Touch-packages] [Bug 1291458] Re: Volume buttons change ringtone volume when screen is off

2016-07-17 Thread Matthew Paul Thomas
** Summary changed:

- Volume buttons change ringtone volume when suspended
+ Volume buttons change ringtone volume when screen is off

** Description changed:

  This is a rather bigger topic for user experience design, but one thing
  that should at least happen asap is volume buttons should be disabled
  when screen is off, otherwise your you-thought-silenced-phone suddenly
  blares a ring tone.
  
  Steps to repro:
  * suspend your phone
  * press volume buttons
  
  Expected result:
  * nothing happens
  
  Current result:
  * volume changes
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140306-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Wed Mar 12 13:14:37 2014
  InstallationDate: Installed on 2014-03-12 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140312)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  
  -
  
- : "While a device is
- asleep, volume keys/buttons should be ignored."
+ : "When the screen is
+ off, to minimize accidental volume changes, the keys should have effect
+ only if any audio is currently playing, and they should not turn on the
+ screen."

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

Title:
  Volume buttons change ringtone volume when screen is off

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is a rather bigger topic for user experience design, but one
  thing that should at least happen asap is volume buttons should be
  disabled when screen is off, otherwise your you-thought-silenced-phone
  suddenly blares a ring tone.

  Steps to repro:
  * suspend your phone
  * press volume buttons

  Expected result:
  * nothing happens

  Current result:
  * volume changes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140306-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Wed Mar 12 13:14:37 2014
  InstallationDate: Installed on 2014-03-12 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140312)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

  -

  : "When the screen is
  off, to minimize accidental volume changes, the keys should have
  effect only if any audio is currently playing, and they should not
  turn on the screen."

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

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


[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

2016-07-17 Thread Matthew Paul Thomas
** Description changed:

  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.
  
  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their device.
  
- --
- 
- the functionality is also covered in the OOBE spec pages 9/10
- 
https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw/edit#
- 
- --
+ : ‘If you insert
+ a new SIM, a “Changing SIM” dialog should appear with the text “To use
+ this new SIM, we need to restart.” and buttons “Later” and “Restart
+ Now”.’
  
  Summary of required work:
-  - enabling ofono hotswap support through environment variable
-  - adding the modal dialog to unity8 side
-  - modify i-network to detect the hotswapping and trickering
-the dialog from unity8
+  - enabling ofono hotswap support through environment variable
+  - adding the modal dialog to unity8 side
+  - modify i-network to detect the hotswapping and trickering
+    the dialog from unity8

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

  : ‘If you
  insert a new SIM, a “Changing SIM” dialog should appear with the text
  “To use this new SIM, we need to restart.” and buttons “Later” and
  “Restart Now”.’

  Summary of required work:
   - enabling ofono hotswap support through environment variable
   - adding the modal dialog to unity8 side
   - modify i-network to detect the hotswapping and trickering
     the dialog from unity8

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

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


[Touch-packages] [Bug 1460458] Re: [system settings] Dual Sim; no possibility to switch on or off each sim card completely.

2016-07-17 Thread Matthew Paul Thomas
Screenshots of the equivalent Android UI: 

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

Title:
  [system settings] Dual Sim; no possibility to switch on or off each
  sim card completely.

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  If two sim cards is used there is no possibility to switch each sim card on 
or off completely
  (to completely activate or deactivate sim 1 and sim 2 separately).

  Sim 1 and sim 2 inside:
  Often I do not want to use both sim cards at the same time.
  Sometimes it's needed that only sim 1 is active.
  Sometimes it's needed that only sim 2 is active.
  Sometimes it's needed that sim 1 and sim 2 is active.

  So there should be the possibility to completely activate/deactivate sim 1 
and sim 2 separately.
  Would be nice in the context menu of the network indicator,
  an on/off switch for sim1 and sim2.
  Or at least in systemsettings.

  Bq Aquaris E4.5
  Ubuntu 14.10 (r22)

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

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


[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

2016-07-17 Thread Matthew Paul Thomas
Specification updated.


** Changed in: ubuntu-ux
   Status: In Progress => Fix Committed

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

  --

  the functionality is also covered in the OOBE spec pages 9/10
  
https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw/edit#

  --

  Summary of required work:
   - enabling ofono hotswap support through environment variable
   - adding the modal dialog to unity8 side
   - modify i-network to detect the hotswapping and trickering
 the dialog from unity8

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

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


[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

2016-07-17 Thread Matthew Paul Thomas
** Changed in: ubuntu-ux
   Status: Confirmed => 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/1332306

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  In Progress
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

  --

  the functionality is also covered in the OOBE spec pages 9/10
  
https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw/edit#

  --

  Summary of required work:
   - enabling ofono hotswap support through environment variable
   - adding the modal dialog to unity8 side
   - modify i-network to detect the hotswapping and trickering
 the dialog from unity8

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

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


[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

2016-07-14 Thread Matthew Paul Thomas
It seems this was never designed. Hot-swap is, by definition, not part
of the “OOBE”.

** Changed in: ubuntu-ux
   Status: Fix Committed => Confirmed

** Changed in: ubuntu-ux
 Assignee: Olga Kemmet (olga-kemmet) => Matthew Paul Thomas (mpt)

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Confirmed
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

  --

  the functionality is also covered in the OOBE spec pages 9/10
  
https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw/edit#

  --

  Summary of required work:
   - enabling ofono hotswap support through environment variable
   - adding the modal dialog to unity8 side
   - modify i-network to detect the hotswapping and trickering
 the dialog from unity8

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

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


[Touch-packages] [Bug 1599295] Re: Apport should not just silently fail when it detects the specific crash report has already been uploaded

2016-07-08 Thread Matthew Paul Thomas
Submitting an error is not supposed to “launch a browser page”. It
hasn’t done that, for release versions of Ubuntu, for four years now.
And you know that it did not “silently fail”, because, as you stated,
trying to resubmit it manually results in “an error saying that the
crash report has been already submitted”. So it had already succeeded.

You can access a linked list of error reports from System Settings >
Security & Privacy > Diagnostics > Show Previous Reports.

** Changed in: apport
   Status: New => Invalid

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

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

Title:
  Apport should not just silently fail when it detects the specific
  crash report has already been uploaded

Status in Apport:
  Invalid
Status in apport package in Ubuntu:
  Invalid

Bug description:
  I have recently been having some trouble with Apport, I asked it to
  submit a crash report however there was a problem and it never
  launched the browser page. Now every time I try to manually submit the
  .crash file I get an error saying that the crash report has been
  already submitted (this is logged in syslog and not anywhere obvious).

  When I use the GUI, and when I use the apport-cli program and ask it
  to submit a report now on the matter it just silently exists without
  telling me anything. So how am I even meant to know what the URL is
  that it has been submitted to?

  So I think that Apport should really not just silently fail and should
  instead tell the user that the crash has already been submitted and
  then actually give them the URL to get to it because otherwise I don't
  know how one is expected to find it unless they get the Apport's
  signature generator working manually or something.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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


[Touch-packages] [Bug 1469535] Re: Blacklist SMS numbers

2016-07-08 Thread Matthew Paul Thomas
It is possible to be deeply convinced of something and still be
mistaken. Ideally, if you block a number, it should block both calls and
messages. But that does not make it “one functionality”. The code for
making calls ring except when they are from a blocked number, and the
code for displaying text messages except when they are from a blocked
number, will be two separate pieces of code. And the UI for blocking a
number from the Phone app, and the UI for blocking a number from the
Messages app, will be one or two more pieces of code. Those three or
four changes might be implemented all at once, but they don’t have to
be.

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

Title:
  Blacklist SMS numbers

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Requirement to blacklist numbers from messaging app to prevent spam or
  abusive texts

  The Phone app equivalent is bug 1469220.

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

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


[Touch-packages] [Bug 1472511] Re: [icons] Some icons are pixelated and don't look good

2016-07-06 Thread Matthew Paul Thomas
*** This bug is a duplicate of bug 1596529 ***
https://bugs.launchpad.net/bugs/1596529

A year later, this hasn’t been fixed in ListItem.Standard, but
apparently it’s fixed in the new ListItems. Marking as a duplicate of a
newer report that has a branch.

** This bug has been marked a duplicate of bug 1596529
   Pixelated icons for rotation, flight mode, about and reset items

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

Title:
  [icons] Some icons are pixelated and don't look good

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

Bug description:
  1. Open System Settings
  2. Notice the icons for: Rotation Lock, Flight Mode, About this phone and 
Reset phone are not as smooth as the other icons. They are jugged, pixelated 
(not sure what is the right English word for that).

  The same is true on any other System Settings screen: icons in list
  items are jagged, while icons outside list items are not.

  Screenshot:
  
https://lh3.googleusercontent.com/-J3X6xqjUulg/VZyaWibESvI/GOE/R0xOVJdCCHk/w400-h720-no/ummm.png

  Zoomed in: https://launchpadlibrarian.net/212617760/1472511-jagged-
  icon.png

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

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


[Touch-packages] [Bug 1587367] Re: Brightness toggle fakes brightness changes

2016-07-06 Thread Matthew Paul Thomas
Bug 1564342 seems to be unrelated: that is about “the rest of the
screen”, that is, the part outside the menu, on a tablet or PC where the
indicator doesn’t take up the whole screen. Your problem here seems to
be that on a phone, there is no “rest of the screen” — the screen is
covered by a black menu where brightness changes make little visible
difference.

Possible solutions include:
a. Nothing — the change in brightness of the text is enough.
b. Remove the brightness slider from the indicator menu.
c. Make indicator menus not black.
d. Make indicator menus full-screen only if they contain at least a screenful 
of stuff, which this one doesn’t.
e. Make this particular menu not full-screen, as a special case.

I would go for (d), but I guess this is up to Paty.

** Changed in: ubuntu-ux
 Assignee: (unassigned) => Paty Davila (dizzypaty)

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

Title:
  Brightness toggle fakes brightness changes

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  New
Status in indicator-power package in Ubuntu:
  New

Bug description:
  When the display brightness is configured from settings -> brightness
  and display, while sliding the slider the user gets a preview of how
  it will look like the chosen value.

  Contrarily, when the brightness is controlled from quick settings,
  since the whole screen is black, the only clue is the brightness of
  the white text around.

  In Android, this is solved by making this screen transparent so the
  user can see the effect of using different values while sliding.

  Product: bq Aquaris E4.5, E5 & M10
  FW version: OTA-10.1
  HW version: MP

  STEPS TO REPRO:
  1. Pull down upper quick settings and check how screen is blackened 
  2. Now from battery toggle change screen brightness

  Actual Result:
  User can not know in advance what their chosen setting will be like

  Expected Result:
  Screen brightness changed from upper quick settings should work the same as 
brightness toggle in settings

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

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


[Touch-packages] [Bug 1549733] Re: SystemSettings Language view: hitting Space on HW keyboard triggers switch even when it (or its list item) does not show any visual focus frame

2016-07-05 Thread Matthew Paul Thomas
It is not and has never been a “requirement” that “Keyboard focus should
follow tap/ click so that pressing (Shift)Tab moves relative to the
component last interacted with”. That would be highly unpleasant if it
applied, for example, to scrollbars, panel resize handles, or window
resize handles. Unfortunately, because the initial toolkit designers
were focused on touch input, the toolkit specification did not make a
distinction between elements that should be focusable and elements that
should not.

So, Femma has just approved my definition of the three focusability
classes for elements, and it is now part of the specification template
for toolkit elements to define which focusability class it belongs to.
She’s also approved my definition of the three selectability classes for
lists. Making lists non-pointer-selectable by default would make *this*
list non-pointer-selectable, which should mean tapping the list item
will not focus its switch, which should mean that Space does not toggle
the switch, which fixes this bug.

To summarize: When most of your input is with touch, it would be ugly
for most controls to get focus rings — and most list items to look
selected — just because you tapped them and *might* use a keyboard to
navigate through them later. The toolkit currently tries to solve this
by suppressing the focused/selected appearance based on *how* the item
was focused/selected. This has turned out to be mistaken because it
results in surprising behavior if you *do* use a keyboard later. A
better solution is that for many types of control — and items in many
lists — tapping/clicking should not focus/select the control in the
first place.

** Changed in: ubuntu-ux
   Status: In Progress => Fix Committed

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

Title:
  SystemSettings Language view: hitting Space on HW keyboard
  triggers switch even when it (or its list item) does not show any
  visual focus frame

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  Nexus7, rc-proposed, r373
  Ubuntu UI Toolkit version r1795

  1) Connect bluetooth keyboard
  2) Open system settings
  3) Open Language & Text view
  4) Press tab until the n-th switch shows its focus frame
  5) Now tap (using touchscreen) on the m-th list item, with  m < n (tap on the 
list item, not on the switch of that list item)
  NOTE: It is important that m < n, the bug will not trigger on listitems that 
have not been focused at least once!
  6) At this point the focus frame around the n-th switch has disappeared
  7) Now press Space on the keyboard

  Expected outcome:
  Nothing, because there is no focus frame anywhere on the screen
  This is confusing for the user as he can never be sure about which item will 
be actioned by the keyboard keys

  Actual outcome:
  The switch of the m-th list item is triggered, even though that list item or 
switch were not showing any focus frame

  : “To avoid errors from unintended focus and
  distraction from irrelevant focus rings, there should be three classes
  of control: … • Non-pointer-focusable: Focusable with Tab … Yes …
  Focusable with pointing device … No”

  : “To avoid distraction from irrelevant
  selection, there should be three classes of list: … • Non-pointer-
  selectable: Selectable with arrow keys … Yes … Selectable with
  pointing device … No … Any list that is non-pointer-selectable should
  be non-pointer-focusable.”

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

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


[Touch-packages] [Bug 1549733] Re: SystemSettings Language view: hitting Space on HW keyboard triggers switch even when it (or its list item) does not show any visual focus frame

2016-07-05 Thread Matthew Paul Thomas
** Description changed:

  Nexus7, rc-proposed, r373
- 
  Ubuntu UI Toolkit version r1795
  
- How to reproduce:
  1) Connect bluetooth keyboard
  2) Open system settings
  3) Open Language & Text view
  4) Press tab until the n-th switch shows its focus frame
  5) Now tap (using touchscreen) on the m-th list item, with  m < n (tap on the 
list item, not on the switch of that list item)
  NOTE: It is important that m < n, the bug will not trigger on listitems that 
have not been focused at least once!
  6) At this point the focus frame around the n-th switch has disappeared
  7) Now press Space on the keyboard
  
  Expected outcome:
  Nothing, because there is no focus frame anywhere on the screen
  This is confusing for the user as he can never be sure about which item will 
be actioned by the keyboard keys
  
  Actual outcome:
  The switch of the m-th list item is triggered, even though that list item or 
switch were not showing any focus frame
  
  : “To avoid errors from unintended focus and
  distraction from irrelevant focus rings, there should be three classes
- of control: … • Non-pointer-focusable: Focusable only by Tabbing or
- other non-pointer input, not by using a pointing device.”
+ of control: … • Non-pointer-focusable: Focusable with Tab … Yes …
+ Focusable with pointing device … No”
  
  : “To avoid distraction from irrelevant
  selection, there should be three classes of list: … • Non-pointer-
- selectable: Any enabled item in the list can be selected using Up or
- Down keys, or by other non-pointer input, but not by using a pointing
- device … Any list that is non-pointer-selectable should be non-pointer-
- focusable.”
+ selectable: Selectable with arrow keys … Yes … Selectable with pointing
+ device … No … Any list that is non-pointer-selectable should be non-
+ pointer-focusable.”

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

Title:
  SystemSettings Language view: hitting Space on HW keyboard
  triggers switch even when it (or its list item) does not show any
  visual focus frame

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  Nexus7, rc-proposed, r373
  Ubuntu UI Toolkit version r1795

  1) Connect bluetooth keyboard
  2) Open system settings
  3) Open Language & Text view
  4) Press tab until the n-th switch shows its focus frame
  5) Now tap (using touchscreen) on the m-th list item, with  m < n (tap on the 
list item, not on the switch of that list item)
  NOTE: It is important that m < n, the bug will not trigger on listitems that 
have not been focused at least once!
  6) At this point the focus frame around the n-th switch has disappeared
  7) Now press Space on the keyboard

  Expected outcome:
  Nothing, because there is no focus frame anywhere on the screen
  This is confusing for the user as he can never be sure about which item will 
be actioned by the keyboard keys

  Actual outcome:
  The switch of the m-th list item is triggered, even though that list item or 
switch were not showing any focus frame

  : “To avoid errors from unintended focus and
  distraction from irrelevant focus rings, there should be three classes
  of control: … • Non-pointer-focusable: Focusable with Tab … Yes …
  Focusable with pointing device … No”

  : “To avoid distraction from irrelevant
  selection, there should be three classes of list: … • Non-pointer-
  selectable: Selectable with arrow keys … Yes … Selectable with
  pointing device … No … Any list that is non-pointer-selectable should
  be non-pointer-focusable.”

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

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


  1   2   3   4   5   6   7   8   9   10   >