[Touch-packages] [Bug 1603194] Re: [osk] An entire emoji quick-jump icon shouldn't be spent on clocks

[Michael Terry]

Ah OK that makes sense.  :)

I couldn't figure out why clocks were so favored.  :P

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

Title:
  [osk] An entire emoji quick-jump icon shouldn't be spent on clocks

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  What is the story with the clock category on the current emoji OSK
  layout?

  We have only six quick-jump buttons.  Clocks would seem like a very
  low priority to me.

  I don't have a suggestion as to what should replace it.  But, like,
  not clocks.

  (Is there any science behind the current layout of emojis / which
  sections the buttons jump to?  I doubt it, because any layout based on
  the most-used or most-relevant would certainly include the poop emoji
  more prominently.)  :P

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

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

[Touch-packages] [Bug 1603194] Re: [osk] An entire emoji quick-jump icon shouldn't be spent on clocks

[Michael Terry]

Looks like clocks still get their own category there?  (Just reading the
source.)  But it is improved...  Instead of "wasting" 1 out of 6
categories, it's only 1 out of 9 categories.

Although it looks like clocks have been moved up to be first category
listed, in front of face emojis!

Maybe I don't understand how people use emojis, and there is wide spread
clamoring for clocks.  But in my eyes, the attached branch does not fix
this bug.

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

Title:
  [osk] An entire emoji quick-jump icon shouldn't be spent on clocks

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  What is the story with the clock category on the current emoji OSK
  layout?

  We have only six quick-jump buttons.  Clocks would seem like a very
  low priority to me.

  I don't have a suggestion as to what should replace it.  But, like,
  not clocks.

  (Is there any science behind the current layout of emojis / which
  sections the buttons jump to?  I doubt it, because any layout based on
  the most-used or most-relevant would certainly include the poop emoji
  more prominently.)  :P

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

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

[Touch-packages] [Bug 1603194] [NEW] [osk] An entire emoji quick-jump icon shouldn't be spent on clocks

[Michael Terry]

Public bug reported:

What is the story with the clock category on the current emoji OSK
layout?

We have only six quick-jump buttons.  Clocks would seem like a very low
priority to me.

I don't have a suggestion as to what should replace it.  But, like, not
clocks.

(Is there any science behind the current layout of emojis / which
sections the buttons jump to?  I doubt it, because any layout based on
the most-used or most-relevant would certainly include the poop emoji
more prominently.)  :P

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

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

Title:
  [osk] An entire emoji quick-jump icon shouldn't be spent on clocks

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  What is the story with the clock category on the current emoji OSK
  layout?

  We have only six quick-jump buttons.  Clocks would seem like a very
  low priority to me.

  I don't have a suggestion as to what should replace it.  But, like,
  not clocks.

  (Is there any science behind the current layout of emojis / which
  sections the buttons jump to?  I doubt it, because any layout based on
  the most-used or most-relevant would certainly include the poop emoji
  more prominently.)  :P

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

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

[Touch-packages] [Bug 1599203] [NEW] CrossFadeImage: modifying sourceSize causes black image

[Michael Terry]

Public bug reported:

1) Have a CrossFadeImage loaded
2) Set a new source
3) Set a new sourceSize for the new source

You'll see the CrossFadeImage go black while it reloads the image for
the new sourceSize.  This rather breaks the point of CrossFadeImage.

Each source may have its own unique sourceSize.  They tend to go hand-
in-hand.  But modifying sourceSize currently affects both image1 and
image2 internally.

Maybe either (A) have a way to set source and sourceSize at the same
time or (B) have sourceSize changes only affect the next-loaded source?

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

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

Title:
  CrossFadeImage: modifying sourceSize causes black image

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

Bug description:
  1) Have a CrossFadeImage loaded
  2) Set a new source
  3) Set a new sourceSize for the new source

  You'll see the CrossFadeImage go black while it reloads the image for
  the new sourceSize.  This rather breaks the point of CrossFadeImage.

  Each source may have its own unique sourceSize.  They tend to go hand-
  in-hand.  But modifying sourceSize currently affects both image1 and
  image2 internally.

  Maybe either (A) have a way to set source and sourceSize at the same
  time or (B) have sourceSize changes only affect the next-loaded
  source?

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

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

[Touch-packages] [Bug 1599163] [NEW] Move unity8's greeter off the "/" DBus path

[Michael Terry]

Public bug reported:

We expose the Greeter DBus API (whether we're active, which user is
selected, etc) on the root / DBus path.  This can easily conflict with
other potential APIs (which are similarly rude as us to claim such a
path).

We should switch away from it.  Potential clients right now:

- indicators
- test tools
- adb
- telephony stack

While switching, it may be wise to move to some more standard APIs as
well, like using logind's LockedHint instead of IsActive.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Michael Terry (mterry)
 Status: New

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  Move unity8's greeter off the "/" DBus path

Status in unity8 package in Ubuntu:
  New

Bug description:
  We expose the Greeter DBus API (whether we're active, which user is
  selected, etc) on the root / DBus path.  This can easily conflict with
  other potential APIs (which are similarly rude as us to claim such a
  path).

  We should switch away from it.  Potential clients right now:

  - indicators
  - test tools
  - adb
  - telephony stack

  While switching, it may be wise to move to some more standard APIs as
  well, like using logind's LockedHint instead of IsActive.

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

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

[Touch-packages] [Bug 1599162] [NEW] Move unity8's greeter off the "/" DBus path

[Michael Terry]

Public bug reported:

We expose the Greeter DBus API (whether we're active, which user is
selected, etc) on the root / DBus path.  This can easily conflict with
other potential APIs (which are similarly rude as us to claim such a
path).

We should switch away from it.  Potential clients right now:

- indicators
- test tools
- adb
- telephony stack

While switching, it may be wise to move to some more standard APIs as
well, like using logind's LockedHint instead of IsActive.

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

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

Title:
  Move unity8's greeter off the "/" DBus path

Status in unity8 package in Ubuntu:
  New

Bug description:
  We expose the Greeter DBus API (whether we're active, which user is
  selected, etc) on the root / DBus path.  This can easily conflict with
  other potential APIs (which are similarly rude as us to claim such a
  path).

  We should switch away from it.  Potential clients right now:

  - indicators
  - test tools
  - adb
  - telephony stack

  While switching, it may be wise to move to some more standard APIs as
  well, like using logind's LockedHint instead of IsActive.

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

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

[Touch-packages] [Bug 1597290] Re: Wallpapers in Windowed Mode are not scaled correctly

[Michael Terry]

My branch updating the default wallpaper [1] makes this a little better.
With that MP, the only blurry wallpapers are portrait-wallpapers-on-a
-landscape-screen (i.e. it fixes the most common case: landscape-
wallpapers).

The proper fix is a little tricky.  We can either (A) load a lot more of
the wallpaper than we might need -- which slows loading down a bit and
is wasteful of memory -- or (B) test-load the wallpaper first to see
it's aspect ratio and adjust how we scale it to avoid the double-scaling
we currently see on portrait wallpapers.  (B) is complicated by the fact
that it would involve changing the sourceSize of the CrossFadeImage
object holding the wallpaper, which currently makes the CrossFadeImage
go to black.  Which kind of defeats the purpose of CrossFadeImage.  So
we may need some toolkit work.

[1] https://code.launchpad.net/~mterry/unity8/default-
wallpaper/+merge/297636

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

Title:
  Wallpapers in Windowed Mode are not scaled correctly

Status in unity8 package in Ubuntu:
  New

Bug description:
  When you set a new wallpaper from the Settings App, if it's a
  landscape wallpaper it will be well scaled if the phone screen is
  horizontal, but when it's vertical it will look blurry. When the
  wallpaper is a portrait picture, it happens the opposite: it is well
  scaled if the screen is vertical but when you rotate it, the wallpaper
  is blurry. Thanks ;)

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

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

[Touch-packages] [Bug 1597290] Re: Wallpapers in Windowed Mode are not scaled correctly

[Michael Terry]

OK cool, will look again tomorrow.

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

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

Title:
  Wallpapers in Windowed Mode are not scaled correctly

Status in unity8 package in Ubuntu:
  New

Bug description:
  When you set a new wallpaper from the Settings App, if it's a
  landscape wallpaper it will be well scaled if the phone screen is
  horizontal, but when it's vertical it will look blurry. When the
  wallpaper is a portrait picture, it happens the opposite: it is well
  scaled if the screen is vertical but when you rotate it, the wallpaper
  is blurry. Thanks ;)

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

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

[Touch-packages] [Bug 1597290] Re: Wallpapers in Windowed Mode are not scaled correctly

[Michael Terry]

I'm not sure I quite understand the complaint and/or can't reproduce it.

If the wallpaper is portrait and you are looking at a landscape screen,
we scale and crop the wallpaper so that the edges of the wallpaper hit
the left and right edge, and crop the top and bottom.  Likewise with
landscape-wallpaper-on-portrait screen.

So there's some scaling there, which might make it a tad blurry.  But
not an insane amount, I wouldn't think (and doesn't seem so on my quick
tests).  Depends on the wallpaper resolution I suppose.

Is there a better thing to do with the wallpaper in that situation?

** Changed in: unity8 (Ubuntu)
   Status: New => 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/1597290

Title:
  Wallpapers in Windowed Mode are not scaled correctly

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  When you set a new wallpaper from the Settings App, if it's a
  landscape wallpaper it will be well scaled if the phone screen is
  horizontal, but when it's vertical it will look blurry. When the
  wallpaper is a portrait picture, it happens the opposite: it is well
  scaled if the screen is vertical but when you rotate it, the wallpaper
  is blurry. Thanks ;)

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

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

[Touch-packages] [Bug 1594874] Re: App won't open from click scope if it got updated in meantime

[Michael Terry]

Well you have more success if you use com.ubuntu.calendar instead of
com.canonical.calendar.  But then you just hit this weird bug where
unity8 acts like it's starting the app but never does?

But yeah, looks like url-dispatcher and ubuntu-app-launch don't handle
short appids very well.  I had thought they did...  But I think it makes
sense to fix that.

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

Title:
  App won't open from click scope if it got updated in meantime

Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  0) Have an app installed that has an available update from the store
  1) Open that app's preview in the click scope
  2) Update the app in System Settings
  3) Click "Open" in the click scope's app preview
  4) Note that the app tries to open, but never does

  Presumably, this is because the click scope is providing a full appid
  including a version.  Either the app preview needs to refresh when an
  update is installed or it needs to provide an appid without a version.

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

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

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

[Michael Terry]

** Changed in: zeromq3 (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  [MIR] zeromq3

Status in zeromq3 package in Ubuntu:
  New

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

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

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

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

  * standards compliance
  FHS and Debian Policy compliant.

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

  * background
  no specific info

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

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

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

[Michael Terry]

** Changed in: content-hub (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  [MIR] content-hub

Status in content-hub package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

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

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

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

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

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

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

[Touch-packages] [Bug 1595569] Re: Indicators panel doesn't close when turning screen off

[Michael Terry]

Naw, I would argue not a feature.  It certainly regressed accidentally.
I've got a fix up for it.

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

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

Title:
  Indicators panel doesn't close when turning screen off

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1594874] Re: App won't open from click scope if it got updated in meantime

[Michael Terry]

Looking at the MP real quick, you need the .desktop at the end of the
application:/// URL.  url-dispatcher doesn't actually look for a
.desktop file itself, but it does ignore any application: URLs that
don't end in .desktop.  It strips it before passing the appid on.

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

Title:
  App won't open from click scope if it got updated in meantime

Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  0) Have an app installed that has an available update from the store
  1) Open that app's preview in the click scope
  2) Update the app in System Settings
  3) Click "Open" in the click scope's app preview
  4) Note that the app tries to open, but never does

  Presumably, this is because the click scope is providing a full appid
  including a version.  Either the app preview needs to refresh when an
  update is installed or it needs to provide an appid without a version.

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

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

[Touch-packages] [Bug 1595569] Re: Indicators panel doesn't close when turning screen off

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  Indicators panel doesn't close when turning screen off

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

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1435923] Re: [greeter/desktop] the password entry is not focused by default

[Michael Terry]

** Summary changed:

- [greeter/desktop] the password entry is not focussed by default
+ [greeter/desktop] the password entry is not focused by default

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

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

Title:
  [greeter/desktop] the password entry is not focused by default

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Using current vivid in desktop mode (desktop-next live session or
  installed), the greeter screen for password has an entry, but this one
  is not getting the keyboard focus by default, which is annoying since
  you can't directly type your password then

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

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

[Touch-packages] [Bug 1586800] Re: Captive portal experience is bad

[Michael Terry]

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

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

Title:
  Captive portal experience is bad

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  If you connect to a wifi AP that uses a captive portal (a login screen
  before granting full internet access, often seen in cafes and hotels)
  with your phone, the experience is quite lacking right now.

  - Webapps won't work. They try to connect to their site, are smart
  enough to know something is wrong when it doesn't get the right site
  back, and never finishes loading anything.

  - Apps in general fail to gracefully handle the case of getting back
  an unexpected result to their connections.

  - You may very reasonably auto connect to a wifi AP and not receive
  notifications for internet services like Telegram until you log in to
  the portal or turn off wifi.

  - If Browser is closed or OOM, when you open it, the last page you
  were at is overridden with the captive portal page. That's lost
  information! I hope you remember what it was.

  - If whatever page you try to go to first on the captive portal
  happens to be an https site, you will get an error instead of the
  portal.

  - If you know what to expect with the captive portal, you basically
  have to open a new browser tab and navigate to a site you have no
  intention of actually using just to get the log in page. It's a bit of
  a farce and not a great UX.

  - If you are *trying* to trigger the captive portal but the site you
  try happens to be cached (in some way? DNS or content caching or
  something), you will see that cached page instead of the portal. Which
  is unexpected for you. (I *think* this happens, maybe I am
  misremembering though.)

  And there are probably more pain points involved. This is just off the
  top of my head. Can we please guide the user through this experience
  instead of leaving them with a system that acts busted?

  Maybe prompt the user and open a page for them? Maybe keep using
  mobile data until the portal is past? Maybe don't tell apps that they
  are connected to the internet when they really aren't? Maybe have the
  Browser not overwrite the last open tab with a portal?

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

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

[Touch-packages] [Bug 1595308] [NEW] Pressing "space" character on OSK with a validator can crash maliit

[Michael Terry]

Public bug reported:

1) Save the code below [1] in a test.qml file
2) Run it on the phone with "qmlscene --desktop_file_hint=dialer-app test.qml"
3) Press the "space" character several times in a row
4) Eventually maliit crashes.  I've attached a crash file from this below.


current build number: 111
device name: turbo
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2016-06-22 12:52:32
version version: 111
version ubuntu: 20160622
version device: 20160617-82a5c0d
version custom: 20160504-975-19-6


[1]
MainView {
  TextField {
 id: field
 anchors.top: parent.top
 anchors.left: parent.left
 anchors.right: parent.right
 inputMethodHints: Qt.ImhDigitsOnly
 validator: RegExpValidator {
regExp: /^\d$/
 }
  }
  Component.onCompleted: field.forceActiveFocus()
}

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

** Attachment added: "_usr_bin_maliit-server.32011.crash"
   
https://bugs.launchpad.net/bugs/1595308/+attachment/4688711/+files/_usr_bin_maliit-server.32011.crash

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

Title:
  Pressing "space" character on OSK with a validator can crash maliit

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  1) Save the code below [1] in a test.qml file
  2) Run it on the phone with "qmlscene --desktop_file_hint=dialer-app test.qml"
  3) Press the "space" character several times in a row
  4) Eventually maliit crashes.  I've attached a crash file from this below.

  
  current build number: 111
  device name: turbo
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2016-06-22 12:52:32
  version version: 111
  version ubuntu: 20160622
  version device: 20160617-82a5c0d
  version custom: 20160504-975-19-6


  [1]
  MainView {
TextField {
   id: field
   anchors.top: parent.top
   anchors.left: parent.left
   anchors.right: parent.right
   inputMethodHints: Qt.ImhDigitsOnly
   validator: RegExpValidator {
  regExp: /^\d$/
   }
}
Component.onCompleted: field.forceActiveFocus()
  }

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

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

[Touch-packages] [Bug 1595308] Re: Pressing "space" character on OSK with a validator can crash maliit

[Michael Terry]

Obviously this should be fixed, but I would also accept a fix for bug
1586435 to avoid needing a validator in the first place.  :)

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

Title:
  Pressing "space" character on OSK with a validator can crash maliit

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  1) Save the code below [1] in a test.qml file
  2) Run it on the phone with "qmlscene --desktop_file_hint=dialer-app test.qml"
  3) Press the "space" character several times in a row
  4) Eventually maliit crashes.  I've attached a crash file from this below.

  
  current build number: 111
  device name: turbo
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2016-06-22 12:52:32
  version version: 111
  version ubuntu: 20160622
  version device: 20160617-82a5c0d
  version custom: 20160504-975-19-6


  [1]
  MainView {
TextField {
   id: field
   anchors.top: parent.top
   anchors.left: parent.left
   anchors.right: parent.right
   inputMethodHints: Qt.ImhDigitsOnly
   validator: RegExpValidator {
  regExp: /^\d$/
   }
}
Component.onCompleted: field.forceActiveFocus()
  }

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

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

[Touch-packages] [Bug 1589242] Re: Turning the mouse on or off unlocks the greeter

[Michael Terry]

I can't reproduce this using a keyboard/mouse bluetooth combo using the
phone/image below.  I looked at the code, but didn't see any obvious
reason this would occur.

current build number: 111
device name: turbo
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2016-06-22 12:52:32
version version: 111
version ubuntu: 20160622
version device: 20160617-82a5c0d
version custom: 20160504-975-19-6

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

Title:
  Turning the mouse on or off unlocks the greeter

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - Ensure you have "no security/swiping" enabled for unlocking.
  - Switch the screen off and on, you get the greeter.
  - If your bluetooth mouse in off, turn it on. If it's on, turn it off.

  Expected result:
  Nothing in particular, the UX of the greeter does not change between desktop 
and staged mode.

  What actually happens:
  The greeter unlocks.

  Note that this doesn't happen if there is a security in place (Pin or
  password) so it's not really a security issue. It also does not happen
  every time, apparently.

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

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

[Touch-packages] [Bug 1435923] Re: [greeter/desktop] the password entry is not focussed by default

[Michael Terry]

** Branch linked: lp:~mterry/unity8/greeter-focus

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

Title:
  [greeter/desktop] the password entry is not focussed by default

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

Bug description:
  Using current vivid in desktop mode (desktop-next live session or
  installed), the greeter screen for password has an entry, but this one
  is not getting the keyboard focus by default, which is annoying since
  you can't directly type your password then

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

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

[Touch-packages] [Bug 1594874] Re: App won't open from click scope if it got updated in meantime

[Michael Terry]

And mightn't the same problem happen on the click scope main list too?
Haven't tested that, but if they include the version, I assume you could
launch an app right before the refresh happens?

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

Title:
  App won't open from click scope if it got updated in meantime

Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  0) Have an app installed that has an available update from the store
  1) Open that app's preview in the click scope
  2) Update the app in System Settings
  3) Click "Open" in the click scope's app preview
  4) Note that the app tries to open, but never does

  Presumably, this is because the click scope is providing a full appid
  including a version.  Either the app preview needs to refresh when an
  update is installed or it needs to provide an appid without a version.

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

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

[Touch-packages] [Bug 1594874] Re: App won't open from click scope if it got updated in meantime

[Michael Terry]

Refreshing the preview is appropriate and good—the icon or description
may have changed. And it will reduce the surface of this bug.

But I suspect that the race condition between clicking on Open and a
refresh and the new click being registered will be unavoidable. I think
it would still make sense for the click scope to not include a version
in its appid URL.

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

Title:
  App won't open from click scope if it got updated in meantime

Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  0) Have an app installed that has an available update from the store
  1) Open that app's preview in the click scope
  2) Update the app in System Settings
  3) Click "Open" in the click scope's app preview
  4) Note that the app tries to open, but never does

  Presumably, this is because the click scope is providing a full appid
  including a version.  Either the app preview needs to refresh when an
  update is installed or it needs to provide an appid without a version.

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

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

[Touch-packages] [Bug 1593718] Re: [desktop] unity8 keeps switching away to greeter after switching users

[Michael Terry]

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  [desktop] unity8 keeps switching away to greeter after switching users

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1) Log into a desktop unity8 session
  2) Go to session indicator and try to switch accounts
  3) You'll end up in the greeter
  4) Now go back to u8 session and you'll notice it auto-switches you to 
greeter again!

  Hard to get back in.  We seem to be constantly trying to switch to
  greeter in a loop or something.

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

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

[Touch-packages] [Bug 1557716] Re: Support 'phone' profile for indicator-session

[Michael Terry]

mpt, but in the converged world, we're trying to strip distinctions
between form factors, though granted, not in all cases.

We have the session indicator in phone images now.  That was by design
request, I believe.

In unity8, we are using the "phone" profile on the desktop too.  It has
come to mean "Converged Touch" rather than phone.  I'm happy to switch
that to something better, but that's what we're doing today.

We don't set a _lockscreen profile yet in unity8, but I'm happy to add
that as part of this bug if indicator-session wants a phone_lockscreen
mode.

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

Title:
  Support 'phone' profile for indicator-session

Status in indicator-session package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When enabling indicator-session support in unity8, we noticed that it
  doesn't have a phone profile?  And in our haste, we kind of worked one
  together unity8-side by stripping some menu items as they came in.

  But it should be done properly upstream.

  Adding a unity8 task so that we know we can drop our hacks when it's
  fixed.

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

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

[Touch-packages] [Bug 1577828] Re: ActivityIndicator should respect theme activity color (i.e. it should be blue)

[Michael Terry]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Michael Terry (mterry) => Zsombor Egri (zsombi)

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

Title:
  ActivityIndicator should respect theme activity color (i.e. it should
  be blue)

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  ActivityIndicator should use the color specified by
  theme.palette.normal.activity instead of hard coding orange, which is
  supposed to be used to indicate focus, not activity.

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

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

[Touch-packages] [Bug 1593880] [NEW] Allow setting a center line for background images

[Michael Terry]

Public bug reported:

Per design doc:
https://docs.google.com/drawings/d/1_yLLkKn3kULoJjsHb5cU72c8muLii0uuxb_CF17VTdk

We are supposed to show background wallpapers cropped and centered on a
user-selectable part of the image (though by default, we should show the
middle of the image, as we do now).

I imagine this would involve a new AccountsService property that gets
updated in sync with BackgroundFile, though this new property would be
on a custom interface instead of on the standard
org.freedesktop.Accounts.User interface.

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

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

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

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

Title:
  Allow setting a center line for background images

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

Bug description:
  Per design doc:
  
https://docs.google.com/drawings/d/1_yLLkKn3kULoJjsHb5cU72c8muLii0uuxb_CF17VTdk

  We are supposed to show background wallpapers cropped and centered on
  a user-selectable part of the image (though by default, we should show
  the middle of the image, as we do now).

  I imagine this would involve a new AccountsService property that gets
  updated in sync with BackgroundFile, though this new property would be
  on a custom interface instead of on the standard
  org.freedesktop.Accounts.User interface.

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

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

[Touch-packages] [Bug 1593841] [NEW] CrossFadeImage: support horizontalAlignment and verticalAlignment

[Michael Terry]

Public bug reported:

CrossFadeImage supports fillMode, which is nice.  But I'd also like to
control horizontalAlignment and verticalAlignment on the inner Image
items.

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

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

Title:
  CrossFadeImage: support horizontalAlignment and verticalAlignment

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

Bug description:
  CrossFadeImage supports fillMode, which is nice.  But I'd also like to
  control horizontalAlignment and verticalAlignment on the inner Image
  items.

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

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

[Touch-packages] [Bug 1593718] [NEW] [desktop] unity8 keeps switching away to greeter after switching users

[Michael Terry]

Public bug reported:

1) Log into a desktop unity8 session
2) Go to session indicator and try to switch accounts
3) You'll end up in the greeter
4) Now go back to u8 session and you'll notice it auto-switches you to greeter 
again!

Hard to get back in.  We seem to be constantly trying to switch to
greeter in a loop or something.

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

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

Title:
  [desktop] unity8 keeps switching away to greeter after switching users

Status in unity8 package in Ubuntu:
  New

Bug description:
  1) Log into a desktop unity8 session
  2) Go to session indicator and try to switch accounts
  3) You'll end up in the greeter
  4) Now go back to u8 session and you'll notice it auto-switches you to 
greeter again!

  Hard to get back in.  We seem to be constantly trying to switch to
  greeter in a loop or something.

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

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

[Touch-packages] [Bug 1577828] Re: ActivityIndicator should respect theme activity color (i.e. it should be blue)

[Michael Terry]

>From the attached MP:

When talking with Paty about this, she said: "The activity
indicator/spinner should also be blue, but I've just checked with Rae
(rae.shambr...@canonical.com // irc: raeshambrook) who is the visual
designer in charge of the colour palette and she said there were some
issues with that spinner. So she is going to check this and confirm
which is the right asset. Sooo... I'll come back to you as soon as she
does."

So I'm waiting on that.  Shall I try to land the blue spinner version
now and re-visit when we have a new asset, or continue waiting?

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

Title:
  ActivityIndicator should respect theme activity color (i.e. it should
  be blue)

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

Bug description:
  ActivityIndicator should use the color specified by
  theme.palette.normal.activity instead of hard coding orange, which is
  supposed to be used to indicate focus, not activity.

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

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

[Touch-packages] [Bug 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

** Changed in: reminders-app (Ubuntu)
   Status: In Progress => Fix Committed

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

** Changed in: dialer-app (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  UbuntuColors considered harmful

Status in webapps-sprint:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in trust-store package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1581047/+subscriptions

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

[Touch-packages] [Bug 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

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

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

Title:
  UbuntuColors considered harmful

Status in webapps-sprint:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in trust-store package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1581047/+subscriptions

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

[Touch-packages] [Bug 1592395] [NEW] Add test to notice when copyrights need updating

[Michael Terry]

Public bug reported:

Right now, we update copyright headers haphazardly.  But it should be
easy to automate.

A line like this should get all the files in bzr that updated this year:

bzr status --short --versioned -r date:2016-01-01.. | grep -v ^-D | grep
-v '^R '

Then we use one of the various copyright update tools in the archive to
check/update those files.  (Something like copyright-update,
licensecheck, license-reconcile, or licensing.  I haven't surveyed them
for which is best for us.)

So we could add a test for this and a convenience script to
automatically update the files that are out of date.

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

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

Title:
  Add test to notice when copyrights need updating

Status in unity8 package in Ubuntu:
  New

Bug description:
  Right now, we update copyright headers haphazardly.  But it should be
  easy to automate.

  A line like this should get all the files in bzr that updated this
  year:

  bzr status --short --versioned -r date:2016-01-01.. | grep -v ^-D |
  grep -v '^R '

  Then we use one of the various copyright update tools in the archive
  to check/update those files.  (Something like copyright-update,
  licensecheck, license-reconcile, or licensing.  I haven't surveyed
  them for which is best for us.)

  So we could add a test for this and a convenience script to
  automatically update the files that are out of date.

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

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

[Touch-packages] [Bug 1591303] [NEW] [webapp-container] No way to allow dynamic user-agent content with --user-agent-string

[Michael Terry]

Public bug reported:

Here's my use case:

1. I have a reddit webapp using webapp-container.
2. I want to avoid reddit's popup box suggesting I install the Android app 
(reddit does this based on the presence of the Android user agent keyword).
3. I want to be convergent and have reddit feed my webapp mobile or desktop 
content as appropriate (reddit will do this for us based on the presence of the 
Mobile user agent keyword).

As of today, #2 makes me want to pass a --user-agent-string without the
"Android" keyword.  But #3 makes me want to allow webapp-container to
use its default dynamic user-agent logic, inserting Mobile or not as
needed.

As a soft #4, I'd also like to have the various versions in the user
agent string be accurate.  Which is hard to do when passing a manual
--user-agent-string.

What would be the best solution to my problem?

My simple proposal would be a new flag that says --no-android-user-agent
or something like that.  But that's a bit grossly named.  Maybe --pure-
user-agent or --native-user-agent or something, which would use a pure
Ubuntu user agent without "Android".

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

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

Title:
  [webapp-container] No way to allow dynamic user-agent content with
  --user-agent-string

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Here's my use case:

  1. I have a reddit webapp using webapp-container.
  2. I want to avoid reddit's popup box suggesting I install the Android app 
(reddit does this based on the presence of the Android user agent keyword).
  3. I want to be convergent and have reddit feed my webapp mobile or desktop 
content as appropriate (reddit will do this for us based on the presence of the 
Mobile user agent keyword).

  As of today, #2 makes me want to pass a --user-agent-string without
  the "Android" keyword.  But #3 makes me want to allow webapp-container
  to use its default dynamic user-agent logic, inserting Mobile or not
  as needed.

  As a soft #4, I'd also like to have the various versions in the user
  agent string be accurate.  Which is hard to do when passing a manual
  --user-agent-string.

  What would be the best solution to my problem?

  My simple proposal would be a new flag that says --no-android-user-
  agent or something like that.  But that's a bit grossly named.  Maybe
  --pure-user-agent or --native-user-agent or something, which would use
  a pure Ubuntu user agent without "Android".

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

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

[Touch-packages] [Bug 1591306] [NEW] [webapp-container] --help needs --app-id

[Michael Terry]

Public bug reported:

To reproduce:

$ webapp-container --help
The application has been launched with no explicit or system provided app id. 
An application id can be set by using the --app-id command line parameter and 
setting it to a unique application specific value or using the APP_ID 
environment variable.

Workaround:

webapp-container --help --app-id=foobar
Usage: webapp-container [-h|--help] ...

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

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

Title:
  [webapp-container] --help needs --app-id

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  To reproduce:

  $ webapp-container --help
  The application has been launched with no explicit or system provided app id. 
An application id can be set by using the --app-id command line parameter and 
setting it to a unique application specific value or using the APP_ID 
environment variable.

  Workaround:

  webapp-container --help --app-id=foobar
  Usage: webapp-container [-h|--help] ...

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

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

[Touch-packages] [Bug 1582987] Re: Have to log in to Unity8 twice (screen is locked after login from lightdm)

[Michael Terry]

OK, I had forgotten we have the --mode argument already in trunk.  Which
means we can solve this today without blocking on the slim_greeter
branch.

I've linked an independent unity8 branch that should fix this.

** No longer affects: unity8-desktop-session (Ubuntu)

** Changed in: unity8 (Ubuntu)
 Assignee: Josh Arenson (josharenson) => Michael Terry (mterry)

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

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

Title:
  Have to log in to Unity8 twice (screen is locked after login from
  lightdm)

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  You have to log in to Unity8 twice on desktop. Once in lightdm and
  again after Unity8 starts.

  The second time is seemingly just the lock screen. But the screen
  should not be locked by default on desktop.

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

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

[Touch-packages] [Bug 1582987] Re: Have to log in to Unity8 twice (screen is locked after login from lightdm)

[Michael Terry]

** Branch unlinked: lp:~josharenson/unity8/slim_greeter_real_lightdm

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

Title:
  Have to log in to Unity8 twice (screen is locked after login from
  lightdm)

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  You have to log in to Unity8 twice on desktop. Once in lightdm and
  again after Unity8 starts.

  The second time is seemingly just the lock screen. But the screen
  should not be locked by default on desktop.

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

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

[Touch-packages] [Bug 1443869] Re: [Edge Education] New wizard in Vivid doesn't excercise indicator gesture

[Michael Terry]

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

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

Title:
  [Edge Education] New wizard in Vivid doesn't excercise indicator
  gesture

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Test case.
  - Flash the device with a recent Vivid image.
  - Complete the wizard.
  - Go through edges demo.

  Expected result.
  - Edges demo exercises the indicator gesture.

  Actual result.
  - Indicators aren't opened.

  current build number: 184
  device name: krillin
  channel: ubuntu-touch/devel-proposed

  
  --- UX Comment ---

  Expected behaviour as per new OOBE and Edge education specification
  (https://docs.google.com/document/d/1pZ-Ro--
  2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s/edit#heading=h.56fezu5i5j0h)

  Top edge education overlay will be trigger when the following is true:

  - 30 seconds after the Left edge gesture is acted on
  - 3 seconds of user's inactivity on the screen

  If the user discovered by himself the notification bar, the Top Edge
  coachmark will not be displayed at all.

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

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

[Touch-packages] [Bug 1484383] Re: [Edge education] Tutorial doesn't teach you about the long swipe from left

[Michael Terry]

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

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

Title:
  [Edge education] Tutorial doesn't teach you about the long swipe from
  left

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I've only just discovered the long swipe from the left to get to the
  apps scope. I feel like an idiot but it turns out it's quite hard to
  find out about or discover accidentally.

  Even the Unity8 tutorial fails to show this feature to the user. You
  can (in fact, must) get through the tutorial using only a short swipe
  from the left to show the launcher. The long swipe remains a somewhat
  hidden feature.

  --- UX Comment ---

  We've included one more instructional overlay in the Edge education
  tutorial that teaches the user how to long swipe from the left to
  access the Today Scope. This is currently being implemented in silo
  33. See spec for further details: https://docs.google.com/document/d
  /1pZ-Ro--
  2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s/edit#heading=h.c3ph00mwjcsp

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

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

[Touch-packages] [Bug 1519779] Re: A PhoneStage gets loaded and unloaded during desktop start up

[Michael Terry]

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

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

Title:
  A PhoneStage gets loaded and unloaded during desktop start up

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce the issue:
  - Launch a unity8-mir session on a desktop/laptop

  Expected outcome:
  No PhoneStage gets loaded

  Actual outcome:
  A PhoneStage, along with a bunch of (fake) applications and surfaces are 
loaded and destroyed.

  Comments:
  Commenting out the Tutorial component in Shell.qml solves the problem.

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

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

[Touch-packages] [Bug 1590447] Re: Error reporting of asio exceptions from AsioDMConnection could be better

[Michael Terry]

(Or at the least use a try/except here and give a nicer message before
dying?)

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

Title:
  Error reporting of asio exceptions from AsioDMConnection could be
  better

Status in Unity System Compositor:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  At least in this one case.

  Josh Arenson and I were debugging a problem with a greeter / lightdm /
  unity-system-compositor.  It turned out to be because lightdm was
  passing unity-system-compositor "--from-dm-fd=0" which resulted in an
  asio exception when it tried to use fd 0.

  But the exception looked like:

  """
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: assign: Operation not permitted
  """

  It took us a surprising amount of effort to track down where this was
  actually failing (which was the
  usc::AsioDMConnection::AsioDMConnection constructor in
  src/asio_dm_connection.cpp).

  I don't have a suggested fix, just a request to make similar failure-
  hunts easier.  Or at the least, this specific error case more obvious.

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

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

[Touch-packages] [Bug 1590447] [NEW] Error reporting could be better

[Michael Terry]

Public bug reported:

At least in this one case.

Josh Arenson and I were debugging a problem with a greeter / lightdm /
unity-system-compositor.  It turned out to be because lightdm was
passing unity-system-compositor "--from-dm-fd=0" which resulted in an
asio exception when it tried to use fd 0.

But the exception looked like:

"""
ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: assign: Operation not permitted
"""

It took us a surprising amount of effort to track down where this was
actually failing (which was the usc::AsioDMConnection::AsioDMConnection
constructor in src/asio_dm_connection.cpp).

I don't have a suggested fix, just a request to make similar failure-
hunts easier.  Or at the least, this specific error case more obvious.

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

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

Title:
  Error reporting could be better

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  At least in this one case.

  Josh Arenson and I were debugging a problem with a greeter / lightdm /
  unity-system-compositor.  It turned out to be because lightdm was
  passing unity-system-compositor "--from-dm-fd=0" which resulted in an
  asio exception when it tried to use fd 0.

  But the exception looked like:

  """
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: assign: Operation not permitted
  """

  It took us a surprising amount of effort to track down where this was
  actually failing (which was the
  usc::AsioDMConnection::AsioDMConnection constructor in
  src/asio_dm_connection.cpp).

  I don't have a suggested fix, just a request to make similar failure-
  hunts easier.  Or at the least, this specific error case more obvious.

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

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

[Touch-packages] [Bug 1435923] Re: [greeter/desktop] the password entry is not focussed by default

[Michael Terry]

** Branch linked: lp:~mterry/unity8/greeter-box

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

Title:
  [greeter/desktop] the password entry is not focussed by default

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Using current vivid in desktop mode (desktop-next live session or
  installed), the greeter screen for password has an entry, but this one
  is not getting the keyboard focus by default, which is annoying since
  you can't directly type your password then

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

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

[Touch-packages] [Bug 1582987] Re: Have to log in to Unity8 twice (screen is locked after login from lightdm)

[Michael Terry]

This is blocked on Josh's split greeter branch (it allows us to launch
unity8 without a greeter loaded).  I'll link it.

** Branch linked: lp:~josharenson/unity8/slim_greeter_real_lightdm

** Changed in: unity8-desktop-session (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => Josh Arenson (josharenson)

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

Title:
  Have to log in to Unity8 twice (screen is locked after login from
  lightdm)

Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  You have to log in to Unity8 twice on desktop. Once in lightdm and
  again after Unity8 starts.

  The second time is seemingly just the lock screen. But the screen
  should not be locked by default on desktop.

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

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

[Touch-packages] [Bug 1586435] Re: Qt.ImhDigitsOnly should only show digits

[Michael Terry]

I've filed upstream bug https://github.com/maliit/framework/issues/31
about this.

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

Title:
  Qt.ImhDigitsOnly should only show digits

Status in maliit-framework package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  When using "inputMethodHints: Qt.ImhDigitsOnly" in an SDK TextField, I
  get a keyboard that includes  a hyphen, a space, a period, and a plus
  (with extended # and * on the plus).

  That looks more like a keyboard I'd expect for
  Qt.ImhFormattedNumbersOnly.

  But I only asked for digits!

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

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

[Touch-packages] [Bug 1586435] Re: Qt.ImhDigitsOnly should only show digits

[Michael Terry]

Adding a maliit task, because it contains the following piece of code,
which just seems broken to me:

if (hints == Qt::ImhFormattedNumbersOnly || hints == Qt::ImhDigitsOnly) {
type = Maliit::NumberContentType;
}

Thus ubuntu-keyboard never has the information it needs to show the
right keyboard.

Changing this in maliit would presumably mean adding a new contentType,
which all maliit consumers would have to support (or suffer breakage)...
:(

** Also affects: maliit-framework (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Qt.ImhDigitsOnly should only show digits

Status in maliit-framework package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  When using "inputMethodHints: Qt.ImhDigitsOnly" in an SDK TextField, I
  get a keyboard that includes  a hyphen, a space, a period, and a plus
  (with extended # and * on the plus).

  That looks more like a keyboard I'd expect for
  Qt.ImhFormattedNumbersOnly.

  But I only asked for digits!

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

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress

[Michael Terry]

Shih-Yuan, I think it would make more sense to just modify wifi-Signal-
on-the-wifi-device-when-its-supplicant-i.patch in place, rather than
creating a patch to patch our patch.  :)

But I've asked cyphermox to check what's happening here, since it seems
odd that his change to src/supplicant-manager/nm-supplicant-interface.c
would be entirely unneeded?

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

Title:
  WiFi malfunction after suspend & resume stress

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)   

 
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2

 
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

[Touch-packages] [Bug 1545844] Re: [webapp-container] App sometimes becomes unresponsive after closing an overlay

[Michael Terry]

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

** This bug has been marked a duplicate of bug 1570828
   Multiple Web Apps crashes when returning from a linked page

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

Title:
  [webapp-container] App sometimes becomes unresponsive after closing an
  overlay

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When using a webapp container on rc-proposed, I've noticed that
  sometimes the app will become unresponsive after closing an overlay.
  It seems to have started in the past week or so?

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

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

[Touch-packages] [Bug 1586435] [NEW] Qt.ImhDigitsOnly should only show digits

[Michael Terry]

Public bug reported:

When using "inputMethodHints: Qt.ImhDigitsOnly" in an SDK TextField, I
get a keyboard that includes  a hyphen, a space, a period, and a plus
(with extended # and * on the plus).

That looks more like a keyboard I'd expect for
Qt.ImhFormattedNumbersOnly.

But I only asked for digits!

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

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

Title:
  Qt.ImhDigitsOnly should only show digits

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  When using "inputMethodHints: Qt.ImhDigitsOnly" in an SDK TextField, I
  get a keyboard that includes  a hyphen, a space, a period, and a plus
  (with extended # and * on the plus).

  That looks more like a keyboard I'd expect for
  Qt.ImhFormattedNumbersOnly.

  But I only asked for digits!

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

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

[Touch-packages] [Bug 1449295] Re: [Icons] Transparent app icon backgrounds look bad

[Michael Terry]

I've added a task for ubuntu-system-settings, because I just remembered
that it also displays app icons: in Storage, App Permissions, and
Notifications.

But note that I'm still waiting on design input.  Copied from the
attached MP:

Paty when I asked about this branch: "Regarding the opinion on the
colour choice for the icons BG, I pinged Mattheiu, who is the icon
designer and he is gonna look into this and hopefully, comment on the
bug ticket. I'm sorry I'm not able to help more on this. I think
porcelain should work well, but I rather not make visual decisions... :
P"

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

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

Title:
  [Icons] Transparent app icon backgrounds look bad

Status in Ubuntu UX:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I uploaded an app with an icon that had a transparent background.

  In the dash, the wallpaper is visible behind the icon.  And in the
  launcher, the icon is presented on a dark background, making it look
  very different than on dash with its white background.

  Neither looks great, and makes the shell look a little janky.
  Obviously, the app author should just fix their icon.  But if they DO
  give us a bad icon, we should fix it for them, else we look bad too.

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

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

[Touch-packages] [Bug 1449295] Re: [Icons] Inconsistent tranparent app icon handling

[Michael Terry]

Looks like the presentation is now consistently transparent.

So that's good, sorta.  I'm now going to change this bug to be about how
transparent backgrounds for icons looks terrible.

I've proposed the attached branch to fix this.

** Summary changed:

- [Icons] Inconsistent tranparent app icon handling
+ [Icons] Transparent app icon backgrounds look bad

** Description changed:

  I uploaded an app with an icon that had a transparent background.
  
- The Ubuntu Store scope renders it with a white background.
- The dash renders it transparent.
- The launcher renders it transparent.
+ In the dash, the wallpaper is visible behind the icon.  And in the
+ launcher, the icon is presented on a dark background, making it look
+ very different than the dash with its white background.
  
- I think the Store is doing the right thing. But any solution is fine, as
- long as it is consistent.
+ Neither looks great, and makes the shell look a little janky.
+ Obviously, the app author should just fix their icon.  But if they DO
+ give us a bad icon, we should fix it for them, else we look bad too.

** Description changed:

  I uploaded an app with an icon that had a transparent background.
  
  In the dash, the wallpaper is visible behind the icon.  And in the
  launcher, the icon is presented on a dark background, making it look
- very different than the dash with its white background.
+ very different than on dash with its white background.
  
  Neither looks great, and makes the shell look a little janky.
  Obviously, the app author should just fix their icon.  But if they DO
  give us a bad icon, we should fix it for them, else we look bad too.

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

Title:
  [Icons] Transparent app icon backgrounds look bad

Status in Ubuntu UX:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I uploaded an app with an icon that had a transparent background.

  In the dash, the wallpaper is visible behind the icon.  And in the
  launcher, the icon is presented on a dark background, making it look
  very different than on dash with its white background.

  Neither looks great, and makes the shell look a little janky.
  Obviously, the app author should just fix their icon.  But if they DO
  give us a bad icon, we should fix it for them, else we look bad too.

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

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

[Touch-packages] [Bug 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

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

** Changed in: reminders-app (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  UbuntuColors considered harmful

Status in webapps-sprint:
  In Progress
Status in reminders-app package in Ubuntu:
  In Progress
Status in trust-store package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1581047/+subscriptions

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

[Touch-packages] [Bug 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

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

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

Title:
  UbuntuColors considered harmful

Status in webapps-sprint:
  In Progress
Status in reminders-app package in Ubuntu:
  New
Status in trust-store package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1581047/+subscriptions

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

[Touch-packages] [Bug 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

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

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  UbuntuColors considered harmful

Status in trust-store package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

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

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

[Touch-packages] [Bug 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

** Changed in: trust-store (Ubuntu)
   Status: New => In Progress

** Changed in: trust-store (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

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

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  UbuntuColors considered harmful

Status in trust-store package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

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

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

[Touch-packages] [Bug 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

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

** Also affects: trust-store (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  UbuntuColors considered harmful

Status in trust-store package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

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

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

[Touch-packages] [Bug 1541971] Re: Review button inactive without explanation

[Michael Terry]

Err, that request might be a duplicate of bug 1580935.

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

Title:
  Review button inactive without explanation

Status in Ubuntu UX:
  Fix Committed
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  If you try to add an app review, there's no visual indication that you
  also need to rate it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160122-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Thu Feb  4 19:09:01 2016
  InstallationDate: Installed on 2016-01-30 (5 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160130-020304)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1541971] Re: Review button inactive without explanation

[Michael Terry]

Relatedly, if you rate the app but do not write a review, the Send
button is enabled and will let you submit it (which is not intended, see
comment #3).

The scope will refresh, but you won't see your review!  Because (I
assume) the review server rejected the textless review.

This bug seems to appear because the click scope specifies "required" =
"review" for preview data [1].  If it specified nothing, both review and
rating would be required, AFAIK.

So there is a further fix in the click scope to drop those lines I
believe.  I've added a task.

[1] http://bazaar.launchpad.net/~ubuntuone-control-tower/unity-scope-
click/trunk/view/head:/libclickscope/click/preview.cpp#L934

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

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

Title:
  Review button inactive without explanation

Status in Ubuntu UX:
  Fix Committed
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  If you try to add an app review, there's no visual indication that you
  also need to rate it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160122-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Thu Feb  4 19:09:01 2016
  InstallationDate: Installed on 2016-01-30 (5 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160130-020304)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1541971] Re: Review button inactive without explanation

[Michael Terry]

(sorry, small typo in my comment #5.  The click scope currently
specifies "required" = "rating".)

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

Title:
  Review button inactive without explanation

Status in Ubuntu UX:
  Fix Committed
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  If you try to add an app review, there's no visual indication that you
  also need to rate it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160122-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Thu Feb  4 19:09:01 2016
  InstallationDate: Installed on 2016-01-30 (5 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160130-020304)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1564351] Re: Unity8 stuck on hint "Long swipe from the left edge to open the Today scope" and can't close it. Desktop left unusable.

[Michael Terry]

Ah I understand what you mean.  It's Fix-Released for the overlay, but
not the distro side of things yet.  Which is what the ubuntu bug tasks
track.  For the overlay, we'd more properly use an Ubuntu RTM task.
Though we rarely bother these days.

Once we land silos in yakkety (and copy overlay packages into yakkety),
this will be Fix-Released for Ubuntu proper as well.

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

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  Unity8 stuck on hint "Long swipe from the left edge to open the Today
  scope" and can't close it. Desktop left unusable.

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

Bug description:
  Can not unlock my desktop, swipe is not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 19:29:50 2016
  InstallationDate: Installed on 2016-03-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1582227] Re: Active header section is blue

[Michael Terry]

Huh.  That surprises me.  Is there a design blog post about the new
colors and what is considered focus vs active vs positive that I could
read?

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

Title:
  Active header section is blue

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  When using sections in the header (either new style Sections object or
  old sections property), the active section is shown with the
  theme.palette.selected.backgroundTertiaryText color.

  Which I don't think is appropriate?  That's for actual selected text,
  like with a mouse or whatever, right?  Which is blue in the current
  themes, the color of "activity".

  But the section isn't selected, it's active.  I'd suggest either green
  ("positive", like we do with active checkboxes) or orange ("focus"
  since it's the currently focused section).

  But blue looks wrong to me.

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

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

[Touch-packages] [Bug 1582242] [NEW] Support a user-session mode for authenticating

[Michael Terry]

Public bug reported:

We talked about this in person in Prague.

Ideally a greeter could run as in the user's session and act as a
lockscreen for the user as well as a way to authenticate/log-in as other
users.

This would let us avoid running a whole other session for the greeter on
the phone, which is memory intensive.

It might be easiest for unity8 if that API was still just liblightdm,
just running in a special mode.  But I'm not picky on how it's done.

There may be security questions around this.  I asked Jamie and Tyler
about it, I'll post any concerns from them.

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Assignee: Robert Ancell (robert-ancell)
 Status: New

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Support a user-session mode for authenticating

Status in lightdm package in Ubuntu:
  New

Bug description:
  We talked about this in person in Prague.

  Ideally a greeter could run as in the user's session and act as a
  lockscreen for the user as well as a way to authenticate/log-in as
  other users.

  This would let us avoid running a whole other session for the greeter
  on the phone, which is memory intensive.

  It might be easiest for unity8 if that API was still just liblightdm,
  just running in a special mode.  But I'm not picky on how it's done.

  There may be security questions around this.  I asked Jamie and Tyler
  about it, I'll post any concerns from them.

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

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

[Touch-packages] [Bug 1582227] [NEW] Active header section is blue

[Michael Terry]

Public bug reported:

When using sections in the header (either new style Sections object or
old sections property), the active section is shown with the
theme.palette.selected.backgroundTertiaryText color.

Which I don't think is appropriate?  That's for actual selected text,
like with a mouse or whatever, right?  Which is blue in the current
themes, the color of "activity".

But the section isn't selected, it's active.  I'd suggest either green
("positive", like we do with active checkboxes) or orange ("focus" since
it's the currently focused section).

But blue looks wrong to me.

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

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

Title:
  Active header section is blue

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

Bug description:
  When using sections in the header (either new style Sections object or
  old sections property), the active section is shown with the
  theme.palette.selected.backgroundTertiaryText color.

  Which I don't think is appropriate?  That's for actual selected text,
  like with a mouse or whatever, right?  Which is blue in the current
  themes, the color of "activity".

  But the section isn't selected, it's active.  I'd suggest either green
  ("positive", like we do with active checkboxes) or orange ("focus"
  since it's the currently focused section).

  But blue looks wrong to me.

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

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

[Touch-packages] [Bug 1564351] Re: Unity8 stuck on hint "Long swipe from the left edge to open the Today scope" and can't close it. Desktop left unusable.

[Michael Terry]

Daniel, this fix did land.  If we're experiencing the same symptoms
again, it might be best to use a new bug indeed.  Might be a different
root cause.

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

Title:
  Unity8 stuck on hint "Long swipe from the left edge to open the Today
  scope" and can't close it. Desktop left unusable.

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

Bug description:
  Can not unlock my desktop, swipe is not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 19:29:50 2016
  InstallationDate: Installed on 2016-03-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

** Branch linked: lp:~mterry/unity8/less-ubuntucolors

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

Title:
  UbuntuColors considered harmful

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

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

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

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

[Touch-packages] [Bug 1572112] Re: Sync maintenance release lcms2 2.7-1 (main) from Debian testing (main)

[Michael Terry]

I think you mean merge, not sync here.  Debian/upstream don't use our
byte-order patch.  But I'll work on a merge for yakkety.

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

Title:
  Sync maintenance release lcms2 2.7-1 (main) from Debian testing (main)

Status in lcms2 package in Ubuntu:
  New

Bug description:
  Please Merge lcms2 2.7-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta:
    * No change rebuild to get debug symbols on all architectures.
    * Merge with Debian, remaining change:
  - debian/patches/byte-order.patch: Use endian.h to determine byte order 
in use.
  

  https://github.com/mm2/Little-CMS/blob/master/ChangeLog

  Fixed a possible segmentation fault in a non-happy path
  Fixed a macro clash on SNONE.
  Added a safety check on named color lists
  Added a function to retrieve the iohandler of a given profile object
  Remove unused vcproj files
  Some maintenance fixes
  utils/jpgicc/iccjpeg.c: Fix check if unsigned variable 'total_length'… …
  Add missing comma in CGATS parser
  Remove dead code.
  Move unused var suppresor before the `return` statements.
  Added a flag to clip negative values in unbounded transforms (only gray, rgb, 
cmyk)
  Added a global optimization that merges consecutive matrices in pipelines. 
Fixes loss of precision in some transforms
  New project for mac
  Added license for iccjpeg.c
  Added a project for VS2013
  Fixed wrong handling of extra channels in some formatters.
  Added an option in transicc for working in bounded mode
  Added a version retrieval function
  

  Changelog entries since current xenial version 2.6-3ubuntu2:

  lcms2 (2.7-1) unstable; urgency=medium

    * Imported Upstream version 2.7 (Closes: 819718)
    * No longer ship own copy of documentation source files
    * Removed patches (applied upstream)
  + update-manpages.patch
  + sanity-check-profiles-CVE-2014-0459.patch
  + endianness-verification-fix-powerpc.patch
    * Move to automatic dbgsym packages
    * Use secure URLs for Version Control System repository
    * Bump Standards version to 3.9.7, no changes needed
    * New patch: dont-write-uninitialized-memory-for-color-strings.patch
  Thanks to Jérémy Bobbio  (Closes: 815248)
    * Update maintainers field (Closes: 820138)

   -- Thomas Weber   Mon, 18 Apr 2016 15:53:10 +0200

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

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

[Touch-packages] [Bug 1578693] Re: Would be useful to expose maximum OSK height

[Michael Terry]

** Branch linked: lp:~mterry/ubuntu-keyboard/report-max-height

** Branch linked: lp:~mterry/qtmir/report-osk-max-height

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

Title:
  Would be useful to expose maximum OSK height

Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  There is a request from Design that on the greeter, we position the
  password input box above the OSK (so that it never has to move when
  the OSK appears).

  For unity8, we could probably hack together something that makes
  assumptions about size of OSK, but that's brittle, especially
  considering the future, when we might have input methods or custom
  keyboards.

  So I'm proposing that we add an UbuntuKeyboardInfo.maximumHeight field
  (and I guess maximumWidth to go with it...).  This would need support
  in ubuntu-keyboard too.

  I don't know the OSK design space super well though, so please provide
  commentary if this could be done a nicer way.

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

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

[Touch-packages] [Bug 1578319] Re: Some ubuntu-ui-toolkit AP tests failing to launch - rejected by unity8 as is using desktop_file_hint

[Michael Terry]

Why is the gallery desktop case different?  If you want to make sure
your test uses that exact content, you could copy it to
~/.local/share/applications.

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

Title:
  Some ubuntu-ui-toolkit AP tests failing to launch - rejected by unity8
  as is using desktop_file_hint

Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  I'm trying to run the ubuntu-ui-toolkit autopilot tests on today's
  image.

  First off, they could cause unity8 to crash, which is bug 1578258 which can 
be resolved with
  https://code.launchpad.net/~gerboland/qtmir/ual-catch-exception/+merge/293805

  That causes unity8 to report it rejects some of the test apps the UITK
  AP test tries to launch:

  qtmir.applications: ApplicationController::createApp - UAL failed to
  create app for appId "ubuntu-ui-toolkit-gallery" : Invalid app ID:
  ubuntu-ui-toolkit-gallery

  UITK AP is launching like this:

  /usr/bin/ubuntu-ui-toolkit-launcher -testability -I  /usr/lib/modules
  /usr/lib/arm-linux-gnueabihf/qt5/examples//ubuntu-ui-toolkit/examples
  /ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml
  --desktop_file_hint=/usr/lib/arm-linux-gnueabihf/qt5/examples/ubuntu-
  ui-toolkit/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-
  gallery.desktop

  which is not using upstart-app-launch - which would explain the fail.
  desktop_file_hint is not a supported means of launching an app (and
  can go away at any time), so UITK should change to use UAL in its AP
  tests.

  This indeed used to work until recently, but a recent refactoring
  broke the desktop_file_hint behaviour. Since it's not a supported
  behaviour, it should not be relied on, so it would be better to fix
  UITK than restore the old behaviour.

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

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

[Touch-packages] [Bug 1578693] [NEW] Would be useful to expose maximum OSK height

[Michael Terry]

Public bug reported:

There is a request from Design that on the greeter, we position the
password input box above the OSK (so that it never has to move when the
OSK appears).

For unity8, we could probably hack together something that makes
assumptions about size of OSK, but that's brittle, especially
considering the future, when we might have input methods or custom
keyboards.

So I'm proposing that we add an UbuntuKeyboardInfo.maximumHeight field
(and I guess maximumWidth to go with it...).  This would need support in
ubuntu-keyboard too.

I don't know the OSK design space super well though, so please provide
commentary if this could be done a nicer way.

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

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

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

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

Title:
  Would be useful to expose maximum OSK height

Status in qtmir package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  There is a request from Design that on the greeter, we position the
  password input box above the OSK (so that it never has to move when
  the OSK appears).

  For unity8, we could probably hack together something that makes
  assumptions about size of OSK, but that's brittle, especially
  considering the future, when we might have input methods or custom
  keyboards.

  So I'm proposing that we add an UbuntuKeyboardInfo.maximumHeight field
  (and I guess maximumWidth to go with it...).  This would need support
  in ubuntu-keyboard too.

  I don't know the OSK design space super well though, so please provide
  commentary if this could be done a nicer way.

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

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

[Touch-packages] [Bug 1578319] Re: Some ubuntu-ui-toolkit AP tests failing to launch - rejected by unity8 as is using desktop_file_hint

[Michael Terry]

So a simple fix would be to ship ubuntu-ui-toolkit-gallery.desktop in
/usr/share/applications.

Another fix would be modify ubuntu-ui-toolkit-launcher to allow teaching
UAL about a custom app on a temporary basis for such custom launches
that aren't apps that we want to ship, but just apps-of-convenience.  To
do this, it could copy the provided desktop file into
~/.local/share/applications and delete it when done.

OR we could add API to UAL that allows using a custom desktop file.

I'm partial to options 1 and/or 2.

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

Title:
  Some ubuntu-ui-toolkit AP tests failing to launch - rejected by unity8
  as is using desktop_file_hint

Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  I'm trying to run the ubuntu-ui-toolkit autopilot tests on today's
  image.

  First off, they could cause unity8 to crash, which is bug 1578258 which can 
be resolved with
  https://code.launchpad.net/~gerboland/qtmir/ual-catch-exception/+merge/293805

  That causes unity8 to report it rejects some of the test apps the UITK
  AP test tries to launch:

  qtmir.applications: ApplicationController::createApp - UAL failed to
  create app for appId "ubuntu-ui-toolkit-gallery" : Invalid app ID:
  ubuntu-ui-toolkit-gallery

  UITK AP is launching like this:

  /usr/bin/ubuntu-ui-toolkit-launcher -testability -I  /usr/lib/modules
  /usr/lib/arm-linux-gnueabihf/qt5/examples//ubuntu-ui-toolkit/examples
  /ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml
  --desktop_file_hint=/usr/lib/arm-linux-gnueabihf/qt5/examples/ubuntu-
  ui-toolkit/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-
  gallery.desktop

  which is not using upstart-app-launch - which would explain the fail.
  desktop_file_hint is not a supported means of launching an app (and
  can go away at any time), so UITK should change to use UAL in its AP
  tests.

  This indeed used to work until recently, but a recent refactoring
  broke the desktop_file_hint behaviour. Since it's not a supported
  behaviour, it should not be relied on, so it would be better to fix
  UITK than restore the old behaviour.

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

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

[Touch-packages] [Bug 1578319] Re: Some ubuntu-ui-toolkit AP tests failing to launch - rejected by unity8 as is using desktop_file_hint

[Michael Terry]

** Description changed:

  I'm trying to run the ubuntu-ui-toolkit autopilot tests on today's
  image.
  
- First off, they could cause unity8 to crash, which is bug 1578258 which can 
be resolved with 
+ First off, they could cause unity8 to crash, which is bug 1578258 which can 
be resolved with
  https://code.launchpad.net/~gerboland/qtmir/ual-catch-exception/+merge/293805
  
  That causes unity8 to report it rejects some of the test apps the UITK
  AP test tries to launch:
  
  qtmir.applications: ApplicationController::createApp - UAL failed to
  create app for appId "ubuntu-ui-toolkit-gallery" : Invalid app ID:
  ubuntu-ui-toolkit-gallery
- 
  
  UITK AP is launching like this:
  
  /usr/bin/ubuntu-ui-toolkit-launcher -testability -I  /usr/lib/modules
  /usr/lib/arm-linux-gnueabihf/qt5/examples//ubuntu-ui-toolkit/examples
  /ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml
  --desktop_file_hint=/usr/lib/arm-linux-gnueabihf/qt5/examples/ubuntu-ui-
  toolkit/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-
  gallery.desktop
  
  which is not using upstart-app-launch - which would explain the fail.
  desktop_file_hint is not a supported means of launching an app (and can
  go away at any time), so UITK should change to use UAL in its AP tests.
  
  This indeed used to work until recently, but a recent refactoring broke
  the desktop_file_hint behaviour. Since it's not a supported behaviour,
- it should be relied on, so it would be better to fix UITK than restore
- the old behaviour.
+ it should not be relied on, so it would be better to fix UITK than
+ restore the old behaviour.

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

Title:
  Some ubuntu-ui-toolkit AP tests failing to launch - rejected by unity8
  as is using desktop_file_hint

Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  I'm trying to run the ubuntu-ui-toolkit autopilot tests on today's
  image.

  First off, they could cause unity8 to crash, which is bug 1578258 which can 
be resolved with
  https://code.launchpad.net/~gerboland/qtmir/ual-catch-exception/+merge/293805

  That causes unity8 to report it rejects some of the test apps the UITK
  AP test tries to launch:

  qtmir.applications: ApplicationController::createApp - UAL failed to
  create app for appId "ubuntu-ui-toolkit-gallery" : Invalid app ID:
  ubuntu-ui-toolkit-gallery

  UITK AP is launching like this:

  /usr/bin/ubuntu-ui-toolkit-launcher -testability -I  /usr/lib/modules
  /usr/lib/arm-linux-gnueabihf/qt5/examples//ubuntu-ui-toolkit/examples
  /ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml
  --desktop_file_hint=/usr/lib/arm-linux-gnueabihf/qt5/examples/ubuntu-
  ui-toolkit/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-
  gallery.desktop

  which is not using upstart-app-launch - which would explain the fail.
  desktop_file_hint is not a supported means of launching an app (and
  can go away at any time), so UITK should change to use UAL in its AP
  tests.

  This indeed used to work until recently, but a recent refactoring
  broke the desktop_file_hint behaviour. Since it's not a supported
  behaviour, it should not be relied on, so it would be better to fix
  UITK than restore the old behaviour.

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

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

[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot

[Michael Terry]

Same here.  On my arale rc-proposed 315 image, I install Authenticator,
run it, click the camera icon, grant it permission, and get a reboot.  I
got it twice in a row, then it worked the third time...  (that time I
was plugged into adb, so maybe that makes a difference?)  Same kernel
stack trace as  comment #7 when it did happen though.

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

Title:
  Opening the camera for the first time leads to reboot

Status in camera-app:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Telegram app:
  Invalid
Status in trust-store:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  --

  Same happens with the following steps:

  1. Flash device (arale) with

  $ ubuntu-device-flash touch --device arale --channel ubuntu/rc-
  proposed/meizu.en --recovery-image 
  --bootstrap

  2. Wait until flash process is done
  3. Go through first-start wizard
  4. Pass tutorial
  5. Directly launch camera-app, approve trust-prompt

  Repeat 1-5 multiple times and you will see a frozen device after step
  5. You can verify it happened due to a kernel panic mentioned in
  comment #7.

  You can reset the trust db entry for the camera app using :
  $rm -rf ~/.local/share/CameraService
  $restart cameraservice-trust-stored

  Run the following to get the command line for all threads so you can match 
the pid from the kmsg later (see below):
  ps H -eo 'pid tid cmd:250 comm'

  To verify it was really the kernel panic run

  $ sudo cat /proc/last_kmsg

  once the device has rebooted.

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

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

[Touch-packages] [Bug 1577828] [NEW] ActivityIndicator should respect theme activity color (i.e. it should be blue)

[Michael Terry]

Public bug reported:

ActivityIndicator should use the color specified by
theme.palette.normal.activity instead of hard coding orange, which is
supposed to be used to indicate focus, not activity.

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

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

Title:
  ActivityIndicator should respect theme activity color (i.e. it should
  be blue)

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

Bug description:
  ActivityIndicator should use the color specified by
  theme.palette.normal.activity instead of hard coding orange, which is
  supposed to be used to indicate focus, not activity.

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

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

[Touch-packages] [Bug 1570922] Re: Initial notifications never shown and not destroyed until unity8 is stopped

[Michael Terry]

Are you sure that you're testing was actually observing the voice mail
notification?

My *guess* is that the voice mail notification happened too early for
unity8 to see it, so it just went to the void.  And the notification
you're seeing is actually the "placeholder" notification.  Which unity-
notification creates and is just an empty notification with the
"placeholder" type.

"What the heck is a placeholder notification?" I hear you ask.  Very
good question.  I'm not 100% sure.  It *seems* to be a hack to move the
notifications lower on the screen?  But I don't know why that's not done
in the UI layer instead of in the notification model...  Honestly, I
don't know if it has any good purpose.  I didn't know about it until I
looked into this bug.

So... it might be confusing your testing.

You can debug this a bit by adding more info into your onCompleted
print: like "summary", "body", and "type".  If type == 0, it's a
placeholder (and summary and body will be empty).  And you can ignore it
if so.

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

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

Title:
  Initial notifications never shown and not destroyed until unity8 is
  stopped

Status in unity-notifications package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1. In Notification.qml add:

Component.onDestruction { console.log("Notification onDestruction");
  }

and a similar log message in Component.onCompleted.
  2. Install dialer-app-autopilot on the phone. This installs a fake phone sim, 
that, among other things, creates a fake voice mail every time unity8 starts.
  3. Restart unity8.
  4. A notification is created for the voice mail,  before unity8 is fully 
drawn. No bubble can be seen, only the green envelope on top. Note that in 
~/.cache/upstart/unity8.log the notification onCompleted log message can be 
seen, but not an onDestruction message.
  5. stop unity8. Note that ~/.cache/upstart/unity8.log now contains the 
onDestruction message.

  Effectively the initial notification is somehow "leaked" and not
  destroyed until the end of the program. This presents a problem in the
  new power architecture model, where unity8 needs to report both when a
  notification is shown (it already does so) and when it is destroyed.

  Notifications sent after unity8 has completed loading are properly
  destroyed when their bubble disappears.

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

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

[Touch-packages] [Bug 1565103] Re: bottom edge first time wizard is being incorrectly displayed on dialer-app and messaging-app

[Michael Terry]

** Branch linked: lp:~mterry/unity8/tutorial-fixups

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

Title:
  bottom edge first time wizard is being incorrectly displayed on
  dialer-app and messaging-app

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

Bug description:
  A new bottom edge wizard is being displayed in the recent images, but
  there are cases where it is being displayed when it shouldn't.

  Steps to reproduce:

  1) Flash the phone with --wipe.
  2) Before opening dialer-app, lock the phone and receive a call.
  3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.

  Another case is when launching messaging-app or dialer-app in a dual
  sim environment. We have a first time dialog that appears behind the
  wizard. Not sure if that's expected, but seems to cause a bad user
  experience to me.

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

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

[Touch-packages] [Bug 1575205] [NEW] Shouldn't the battery-charging icon be blue instead of green?

[Michael Terry]

Public bug reported:

In the suru theme, the battery-XXX-charging icons use green as a "this
is charging" indication.

But with the new suru color updates from Design, I could see an argument
that this color should be blue instead.

Green is used for "positive" things (like default buttons, checked
boxes, or "on" switches).  Blue is used for progress bars and values
that are in a range / more complicated than on or off (e.g. volume).

While "charging" is indeed the positive state of "charging / not
charging", the amount of charge strikes me as a blue thing (the battery
is filling up like a progress bar).

I dunno.  Just wanted to see what Design thought about it.

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

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

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

Title:
  Shouldn't the battery-charging icon be blue instead of green?

Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In the suru theme, the battery-XXX-charging icons use green as a "this
  is charging" indication.

  But with the new suru color updates from Design, I could see an
  argument that this color should be blue instead.

  Green is used for "positive" things (like default buttons, checked
  boxes, or "on" switches).  Blue is used for progress bars and values
  that are in a range / more complicated than on or off (e.g. volume).

  While "charging" is indeed the positive state of "charging / not
  charging", the amount of charge strikes me as a blue thing (the
  battery is filling up like a progress bar).

  I dunno.  Just wanted to see what Design thought about it.

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

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

[Touch-packages] [Bug 1574048] [NEW] Panel appears white for a second when unity8 starts

[Michael Terry]

Public bug reported:

On boot, when unity8 starts drawing itself on the screen, the panel
first appears lightly colored (grey). I'm assuming it is drawing itself
in the light theme first, before switching to suru dark.

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

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

Title:
  Panel appears white for a second when unity8 starts

Status in unity8 package in Ubuntu:
  New

Bug description:
  On boot, when unity8 starts drawing itself on the screen, the panel
  first appears lightly colored (grey). I'm assuming it is drawing
  itself in the light theme first, before switching to suru dark.

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

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

[Touch-packages] [Bug 1545844] Re: [webapp-container] App sometimes becomes unresponsive after closing an overlay

[Michael Terry]

Yeah.  Same symptoms (though that OP mentions magnifying as part of
their repro steps, which for me doesn't automatically trigger it).

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

Title:
  [webapp-container] App sometimes becomes unresponsive after closing an
  overlay

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When using a webapp container on rc-proposed, I've noticed that
  sometimes the app will become unresponsive after closing an overlay.
  It seems to have started in the past week or so?

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

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

[Touch-packages] [Bug 1545844] Re: [webapp-container] App sometimes becomes unresponsive after closing an overlay

[Michael Terry]

Yeah it was.  That was annoying for a bit.  :)

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

Title:
  [webapp-container] App sometimes becomes unresponsive after closing an
  overlay

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When using a webapp container on rc-proposed, I've noticed that
  sometimes the app will become unresponsive after closing an overlay.
  It seems to have started in the past week or so?

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

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

[Touch-packages] [Bug 1571954] [NEW] .co.uk is an odd keyboard option for en_US locales

[Michael Terry]

Public bug reported:

When typing a URL, the '.com' button has long-press alternate text of
'.co.uk ' (in the en_US locale)

This might make sense for en_GB, but US?

I don't have an obvious alternative, but maybe .org?

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

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

Title:
  .co.uk is an odd keyboard option for en_US locales

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  When typing a URL, the '.com' button has long-press alternate text of
  '.co.uk ' (in the en_US locale)

  This might make sense for en_GB, but US?

  I don't have an obvious alternative, but maybe .org?

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

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

[Touch-packages] [Bug 1545844] Re: [webapp-container] App sometimes becomes unresponsive after closing an overlay

[Michael Terry]

Yeah, I don't have a reliable reproduction sequence. I get it in 'The
Old Reader' and 'refdit mobile' apps (theoldreader.mterry and
redditmobile.mterry) but probably only because they both create lots kph
overlays.

One clue is that afyer a restart, the overlay is opened, so the app
didn't get as far as fibishing recording that the overlay was closed.

Sorry for typos, I'm experiencing a separate bug with backspace.

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

Title:
  [webapp-container] App sometimes becomes unresponsive after closing an
  overlay

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When using a webapp container on rc-proposed, I've noticed that
  sometimes the app will become unresponsive after closing an overlay.
  It seems to have started in the past week or so?

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

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

[Touch-packages] [Bug 1545844] Re: [webapp-container] App sometimes becomes unresponsive after closing an overlay

[Michael Terry]

This is still present. Now on stable channel.

Anyone else noticing this?

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

Title:
  [webapp-container] App sometimes becomes unresponsive after closing an
  overlay

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When using a webapp container on rc-proposed, I've noticed that
  sometimes the app will become unresponsive after closing an overlay.
  It seems to have started in the past week or so?

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

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

[Touch-packages] [Bug 1456195] Re: Zero-minimum possessive groups does not match empty string

[Michael Terry]

Nope, that was just a brain fart on my part.  I've uploaded to wily too
now, thanks.

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

** Changed in: pcre3 (Ubuntu Wily)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  Zero-minimum possessive groups does not match empty string

Status in pcre3 package in Ubuntu:
  Fix Released
Status in pcre3 source package in Trusty:
  In Progress
Status in pcre3 source package in Wily:
  In Progress
Status in pcre3 source package in Xenial:
  Fix Released

Bug description:
  The 14.04/15.04 pcre version doesn't match some inputs with possessive
  qualfiers:

  $ echo '"a"'|pcregrep '("([^b"]*+(b.)?)*+")*+'
  $

  Earlier versions (10.04, 12.04):
  $ echo '"a"'|pcregrep '("([^b"]*+(b.)?)*+")*+'
  "a"
  $

  this is fixed with the following upstream commit (that applies cleanly
  to the 15.04 pcre):

  http://vcs.pcre.org/pcre?view=revision=1478

  https://lists.exim.org/lurker/message/20140527.131833.2fd7547c.html

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

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

[Touch-packages] [Bug 1456195] Re: Zero-minimum possessive groups does not match empty string

[Michael Terry]

The wily patch doesn't apply cleanly (there have been releases in
-updates since wily got released).

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

Title:
  Zero-minimum possessive groups does not match empty string

Status in pcre3 package in Ubuntu:
  Fix Released
Status in pcre3 source package in Trusty:
  In Progress
Status in pcre3 source package in Wily:
  Confirmed
Status in pcre3 source package in Xenial:
  Fix Released

Bug description:
  The 14.04/15.04 pcre version doesn't match some inputs with possessive
  qualfiers:

  $ echo '"a"'|pcregrep '("([^b"]*+(b.)?)*+")*+'
  $

  Earlier versions (10.04, 12.04):
  $ echo '"a"'|pcregrep '("([^b"]*+(b.)?)*+")*+'
  "a"
  $

  this is fixed with the following upstream commit (that applies cleanly
  to the 15.04 pcre):

  http://vcs.pcre.org/pcre?view=revision=1478

  https://lists.exim.org/lurker/message/20140527.131833.2fd7547c.html

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

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

[Touch-packages] [Bug 1456195] Re: Zero-minimum possessive groups does not match empty string

[Michael Terry]

Thank you Arne!  I've uploaded the trusty patch, please help test when
it gets published in -proposed.

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

** Changed in: pcre3 (Ubuntu Trusty)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  Zero-minimum possessive groups does not match empty string

Status in pcre3 package in Ubuntu:
  Fix Released
Status in pcre3 source package in Trusty:
  In Progress
Status in pcre3 source package in Wily:
  Confirmed
Status in pcre3 source package in Xenial:
  Fix Released

Bug description:
  The 14.04/15.04 pcre version doesn't match some inputs with possessive
  qualfiers:

  $ echo '"a"'|pcregrep '("([^b"]*+(b.)?)*+")*+'
  $

  Earlier versions (10.04, 12.04):
  $ echo '"a"'|pcregrep '("([^b"]*+(b.)?)*+")*+'
  "a"
  $

  this is fixed with the following upstream commit (that applies cleanly
  to the 15.04 pcre):

  http://vcs.pcre.org/pcre?view=revision=1478

  https://lists.exim.org/lurker/message/20140527.131833.2fd7547c.html

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

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

[Touch-packages] [Bug 1568082] [NEW] Dash 'activity pulse' on bottom should be blue

[Michael Terry]

Public bug reported:

Per new design palette, blue is for activity. Currently that pulser is
orange.

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

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

Title:
  Dash 'activity pulse' on bottom should be blue

Status in unity8 package in Ubuntu:
  New

Bug description:
  Per new design palette, blue is for activity. Currently that pulser is
  orange.

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

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

[Touch-packages] [Bug 1567941] [NEW] [webapp-container] Header text hard to read on light theme-color backgrounds

[Michael Terry]

Public bug reported:

To reproduce in the wild:

1) Install "reddit mobile" app (redditmobile.mterry)
2) Open it, navigate to r/germany

See attached screenshot for that example.

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

** Attachment added: "screenshot20160408_092239991.png"
   
https://bugs.launchpad.net/bugs/1567941/+attachment/4629053/+files/screenshot20160408_092239991.png

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

Title:
  [webapp-container] Header text hard to read on light theme-color
  backgrounds

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  To reproduce in the wild:

  1) Install "reddit mobile" app (redditmobile.mterry)
  2) Open it, navigate to r/germany

  See attached screenshot for that example.

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

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

[Touch-packages] [Bug 1565103] Re: bottom edge first time wizard is being incorrectly displayed on dialer-app and messaging-app

[Michael Terry]

I can't reproduce the live call problem.  For me, the bottom edge hint
waits until the phone call is over.  However, there ARE about 2 seconds
after the phone call ends and the hint appears before the live call view
switches to the normal dialer view.  For those three seconds, the bottom
edge of the dialer-app isn't active.

Is that what you're seeing?  Or something new?

So the two problems I know about now:
- 2 seconds after received call ends
- dialer and messaging apps with 2 SIMs

For fixing the 2-second problem, I could do a hack like "wait 2 seconds
before showing bottom edge for dialer" but that creates more problems.
The user can enter the settings screen in those two seconds.  Which also
doesn't have a bottom edge.  That's why the bottom hints come up as soon
as you open the app for the first time, it is the only time we know
what's on the screen (at least that was the hope).

For fixing the 2-SIM problem, we could probably do a hack that skips the
bottom edge completely on those two apps if you have 2 SIMs in.  But
that also kind of sucks, since those users would probably like the hint
too.  And it gets into brittle cross-domain assumptions between the app
and the shell.

So I guess we very quickly came to the breaking point on the shell being
able to fake knowing when to show bottom edge hints.

Long term, we wanted to bring these hints into the apps anyway.  That's
still the best fix for this.  So we can either speed up that plan, or
implement some quick-and-dirty communication mechanism between these
apps and the shell for when they have an available bottom edge.  Maybe
as simple as exposing a bool on a DBus interface that the shell can
listen to.  Just as a stop-gap to moving the screens.

I'll talk with Design about where we are with that plan.

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

Title:
  bottom edge first time wizard is being incorrectly displayed on
  dialer-app and messaging-app

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

Bug description:
  A new bottom edge wizard is being displayed in the recent images, but
  there are cases where it is being displayed when it shouldn't.

  Steps to reproduce:

  1) Flash the phone with --wipe.
  2) Before opening dialer-app, lock the phone and receive a call.
  3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.

  Another case is when launching messaging-app or dialer-app in a dual
  sim environment. We have a first time dialog that appears behind the
  wizard. Not sure if that's expected, but seems to cause a bad user
  experience to me.

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

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

[Touch-packages] [Bug 1567430] [NEW] [webapp-container] Controls in header need same theme-color adjustments that text gets

[Michael Terry]

Public bug reported:

This is a follow-on issue to bug 1548573.

In that bug, text color now is a more responsive to the background color
of the header, chosen by "theme-color" in CSS.

But the controls of the header (back, forward, refresh) stay grey.
Which is hard to see on some colors.  They should become the same color
as the header text.

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

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

Title:
  [webapp-container] Controls in header need same theme-color
  adjustments that text gets

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  This is a follow-on issue to bug 1548573.

  In that bug, text color now is a more responsive to the background
  color of the header, chosen by "theme-color" in CSS.

  But the controls of the header (back, forward, refresh) stay grey.
  Which is hard to see on some colors.  They should become the same
  color as the header text.

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

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

[Touch-packages] [Bug 1566733] Re: [arale] hardare button interferes with proximity sensor during calls

[Michael Terry]

Looking at code real quick, looks like this is entirely inside of USC
then.  It handles turning on the screen on a key press and knows about
proximity status.

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

Title:
  [arale] hardare button interferes with proximity sensor during calls

Status in Canonical System Image:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  current build number: 299
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Test Case
  1. Make a call to DUT
  2. Answer the call
  3. Cover the proximity sensor and verify that the display turns off
  4. Cover the hardware button 

  Actual Result
  Display turns on even if the proximity sensor is covered

  Expected Result
  Display must not turn on, otherwise the user may start tapping the screen 
with his ears.

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

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

[Touch-packages] [Bug 1566733] Re: [arale] hardare button interferes with proximity sensor during calls

[Michael Terry]

Yup Saviq, that's exactly right.  I just tested with a BT keyboard.  I
pressed a key and the screen turned back on.

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

Title:
  [arale] hardare button interferes with proximity sensor during calls

Status in Canonical System Image:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  current build number: 299
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Test Case
  1. Make a call to DUT
  2. Answer the call
  3. Cover the proximity sensor and verify that the display turns off
  4. Cover the hardware button 

  Actual Result
  Display turns on even if the proximity sensor is covered

  Expected Result
  Display must not turn on, otherwise the user may start tapping the screen 
with his ears.

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

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

[Touch-packages] [Bug 1565818] Re: Disable hardware home button on arale when greeter is active

[Michael Terry]

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

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

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

Title:
  Disable hardware home button on arale when greeter is active

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

Bug description:
  current build number: 298
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  On devices with a hardware button, tapping on it when on the greeter
  dismisses the greater and reveals the keypad to unlock the screen. If,
  for some reason, the display turns on (power button pressed
  inadvertently or battery notification for example) while the device is
  in a pocket, the button is pressed, the greeter dismissed and the
  pocket starts tapping random keys until the device is completely
  locked.

  This button must be disabled when the device is locked.

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

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

[Touch-packages] [Bug 1565818] Re: Disable hardware home button on arale when greeter is active

[Michael Terry]

** Summary changed:

- Disable hardware home button on arale
+ Disable hardware home button on arale when greeter is active

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

Title:
  Disable hardware home button on arale when greeter is active

Status in Canonical System Image:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Opinion
Status in unity8 package in Ubuntu:
  New

Bug description:
  current build number: 298
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  On devices with a hardware button, tapping on it when on the greeter
  dismisses the greater and reveals the keypad to unlock the screen. If,
  for some reason, the display turns on (power button pressed
  inadvertently or battery notification for example) while the device is
  in a pocket, the button is pressed, the greeter dismissed and the
  pocket starts tapping random keys until the device is completely
  locked.

  This button must be disabled when the device is locked.

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

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

[Touch-packages] [Bug 1566295] Re: When displaying the selected timezone, we should show the city the user picked

[Michael Terry]

** Branch linked: lp:~mterry/ubuntu-system-settings/timezone-name

** Branch linked: lp:~mterry/unity8/timezone-name

** Description changed:

  Currently, if I search timezones for Boston, and select Boston in the
- results, the Time & Date page will display "America/New York" as the
- timezone.  Which is not super user friendly.
- 
- It gets worse once we land translation support for geonames [1].  The
- user might pick 波士顿 and we'll still show "America/New York", which they
- might not even be able to read.
+ results, the Time & Date page will display "New York" as the timezone.
+ Which is not super user friendly.
  
  On the desktop, we save the city name the user picks alongside the ISO
  timezone name.  Specifically, it's stored in gsettings:
  "com.canonical.indicator.datetime" schema, key "timezone-name".  It's
  stored like "TIMEZONE NAME" -- that is, the ISO timezone followed by one
  space, followed by the user visible name for that timezone.
  
  Indicator-datetime and unity-control-center already support that key.
  We should too (I guess we should set it in addition to calling
  org.freedesktop.timedate1.SetTimezone).  It might mean extending the
  time-date plugin's SetTimezone call to take two arguments -- the
  timezone and the name.
  
  This change should be coordinated with unity8, which also sets the
  timezone on the first device boot.
- 
- [1]
- https://code.launchpad.net/~mterry/geonames/translations/+merge/288443

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

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  When displaying the selected timezone, we should show the city the
  user picked

Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  New

Bug description:
  Currently, if I search timezones for Boston, and select Boston in the
  results, the Time & Date page will display "New York" as the timezone.
  Which is not super user friendly.

  On the desktop, we save the city name the user picks alongside the ISO
  timezone name.  Specifically, it's stored in gsettings:
  "com.canonical.indicator.datetime" schema, key "timezone-name".  It's
  stored like "TIMEZONE NAME" -- that is, the ISO timezone followed by
  one space, followed by the user visible name for that timezone.

  Indicator-datetime and unity-control-center already support that key.
  We should too (I guess we should set it in addition to calling
  org.freedesktop.timedate1.SetTimezone).  It might mean extending the
  time-date plugin's SetTimezone call to take two arguments -- the
  timezone and the name.

  This change should be coordinated with unity8, which also sets the
  timezone on the first device boot.

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

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

[Touch-packages] [Bug 1566295] Re: When displaying the selected timezone, we should show the city the user picked

[Michael Terry]

** Description changed:

  Currently, if I search timezones for Boston, and select Boston in the
  results, the Time & Date page will display "America/New York" as the
  timezone.  Which is not super user friendly.
  
  It gets worse once we land translation support for geonames [1].  The
  user might pick 波士顿 and we'll still show "America/New York", which they
  might not even be able to read.
  
  On the desktop, we save the city name the user picks alongside the ISO
- timezone name.  Maybe even in the same field?  I don't remember how we
- do it.  But we should just do that.
+ timezone name.  Specifically, it's stored in gsettings:
+ "com.canonical.indicator.datetime" schema, key "timezone-name".  It's
+ stored like "TIMEZONE NAME" -- that is, the ISO timezone followed by one
+ space, followed by the user visible name for that timezone.
+ 
+ Indicator-datetime and unity-control-center already support that key.
+ We should too (I guess we should set it in addition to calling
+ org.freedesktop.timedate1.SetTimezone).  It might mean extending the
+ time-date plugin's SetTimezone call to take two arguments -- the
+ timezone and the name.
+ 
+ This change should be coordinated with unity8, which also sets the
+ timezone on the first device boot.
  
  [1]
  https://code.launchpad.net/~mterry/geonames/translations/+merge/288443

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

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

Title:
  When displaying the selected timezone, we should show the city the
  user picked

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

Bug description:
  Currently, if I search timezones for Boston, and select Boston in the
  results, the Time & Date page will display "America/New York" as the
  timezone.  Which is not super user friendly.

  It gets worse once we land translation support for geonames [1].  The
  user might pick 波士顿 and we'll still show "America/New York", which
  they might not even be able to read.

  On the desktop, we save the city name the user picks alongside the ISO
  timezone name.  Specifically, it's stored in gsettings:
  "com.canonical.indicator.datetime" schema, key "timezone-name".  It's
  stored like "TIMEZONE NAME" -- that is, the ISO timezone followed by
  one space, followed by the user visible name for that timezone.

  Indicator-datetime and unity-control-center already support that key.
  We should too (I guess we should set it in addition to calling
  org.freedesktop.timedate1.SetTimezone).  It might mean extending the
  time-date plugin's SetTimezone call to take two arguments -- the
  timezone and the name.

  This change should be coordinated with unity8, which also sets the
  timezone on the first device boot.

  [1]
  https://code.launchpad.net/~mterry/geonames/translations/+merge/288443

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

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

[Touch-packages] [Bug 1514250] Re: [touch] Can't record with front facing camera

[Michael Terry]

This is fixed now in rc-proposed, presumably by
https://code.launchpad.net/~uriboni/qtubuntu-camera/cameras-
info/+merge/286283

** No longer affects: qtmultimedia-opensource-src (Ubuntu)

** Changed in: qtubuntu-camera (Ubuntu)
   Status: New => Fix Released

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

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

Title:
  [touch] Can't record with front facing camera

Status in Canonical System Image:
  Fix Committed
Status in qtubuntu-camera package in Ubuntu:
  Fix Released

Bug description:
  Using "position: Camera.FrontFace" does nothing on Touch images.  The
  sample qml app below continues to use the back camera.

  ===

  import QtQuick 2.4
  import QtMultimedia 5.4
  import Ubuntu.Components 1.3

  MainView {
  id: root
  applicationName: "testing.testing"

  width: units.gu(100)
  height: units.gu(75)

  Page {
  title: i18n.tr("Testing")

  VideoOutput {
  anchors.fill: parent
  source: camera

  Camera {
  id: camera
  position: Camera.FrontFace
  }
  }
  }
  }

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

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

[Touch-packages] [Bug 1564351] Re: "Swipe from the left edge to open the launcher" - do not work on the desktop

[Michael Terry]

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Opinion

** Changed in: unity8 (Ubuntu)
   Status: Opinion => 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/1564351

Title:
  "Swipe from the left edge to open the launcher" - do not work on the
  desktop

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Can not unlock my desktop, swipe is not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 19:29:50 2016
  InstallationDate: Installed on 2016-03-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1564351] Re: "Swipe from the left edge to open the launcher" - do not work on the desktop

[Michael Terry]

Hrm.  So to reproduce, install unity8 on the desktop and then:

1) sudo gdbus call --system --dest org.freedesktop.Accounts --object-path 
/org/freedesktop/Accounts/User1000 --method org.freedesktop.DBus.Properties.Set 
com.canonical.unity.AccountsService demo-edges ''
2) gsettings set com.canonical.Unity8 usage-mode Staged

(Replace 1000 in step #1 with your UID.)

The problem is that the tutorial is thus fooled about what mode we're
running in (it thinks tablet/phone).

The left-edge tutorial bits assume a touch screen.  And they don't run
in desktop mode (when there is at least one pointer).  So everything
*should* work, except that usage-mode was overridden.

I think since we no longer treat the gsettings value as a user-setting
(unity8 will override it at will), we should re-evaluate it on startup.
That should avoid this particular scenario.

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

Title:
  "Swipe from the left edge to open the launcher" - do not work on the
  desktop

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Can not unlock my desktop, swipe is not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 19:29:50 2016
  InstallationDate: Installed on 2016-03-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1564351] Re: "Swipe from the left edge to open the launcher" - do not work on the desktop

[Michael Terry]

To work around this bug, enter the following in a console:

sudo gdbus call --system --dest org.freedesktop.Accounts --object-path
/org/freedesktop/Accounts/UserXXX --method
org.freedesktop.DBus.Properties.Set com.canonical.unity.AccountsService
demo-edges ''

Where XXX is your UID (the number given when you type "id -u").

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

Title:
  "Swipe from the left edge to open the launcher" - do not work on the
  desktop

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Can not unlock my desktop, swipe is not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 19:29:50 2016
  InstallationDate: Installed on 2016-03-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1564351] Re: "Swipe from the left edge to open the launcher" - do not work on the desktop

[Michael Terry]

Looks like the tutorial thinks its on a phone instead of a desktop.
It's supposed to skip that screen on the desktop.  I'm guessing at one
point you changed the windowed mode to be staged or something?

I'll look at if we can be cleverer.

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  "Swipe from the left edge to open the launcher" - do not work on the
  desktop

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Can not unlock my desktop, swipe is not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 19:29:50 2016
  InstallationDate: Installed on 2016-03-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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