[Touch-packages] [Bug 1605218] Re: Google account login using 2FA isn’t remembered across sessions

[Olli Ries]

I can confirm that Chrome does not show that behavior, i.e. it does let
me login without having to enter the credentials again.

Chromium however does show the behavior described in comment #1.

However, webbrowser-app does require the userid (email) entered again
before letting you log in.

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

Title:
  Google account login using 2FA isn’t remembered across sessions

Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  This has been reliably reproduced on desktop and a phone running
  webbrowser-app 0.23+16.04.20160711-0ubuntu1 (and oxide
  1.15.8-0ubuntu0.16.04.1).

  Steps to reproduce:
  1) wipe your session data (make a backup first if you care) by removing 
~/.local/share/webbrowser-app/
  2) launch webbrowser-app
  3) browse to https://mail.google.com
  4) log in with an account that uses 2FA (I’m testing with a @canonical.com 
address)
  5) read your e-mails
  6) close the browser window
  7) launch webbrowser-app again

  Expected result: you’re back to your inbox, logged in and ready to
  work

  Actual result: google prompts you for your e-mail address. Once
  entered, the login happens automatically, there is no need to do the
  2FA dance again.

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

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

[Touch-packages] [Bug 1517058] Re: network manager does not connect to AP anymore

[Olli Ries]

downgrading the respective firmware to an older release helped.

the system was loading iwlwifi-7260-15.ucode which seemed to be the
source of trouble. Removing any firmware but iwlwifi-7260-10.ucode
allows me to reliably connect to my network again.

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

Title:
  network manager does not connect to AP anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  network manager does not connect to my AP anymore, tries to
  authenticate and then asks for a password (of a previously connected
  wifi network). Upon entering the right password manually and/or
  verifying the stored password is correct the connection still fails.

  I have not been able to get a concise list of actions that get me connected, 
but a wild mix of:
  rmmod iwlmvm iwlwifi
  modprobe iwlmvm iwlwifi
  killall wpa_supplicant
  iwlist scanning
  (dis-/enabling networking in NWmgr)
  (dis-/enabling wifi in NWmgr) 

  gets me back online

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

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

[Touch-packages] [Bug 1517058] Re: network manager does not connect to AP anymore

[Olli Ries]

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1517058/+attachment/4520668/+files/syslog

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

Title:
  network manager does not connect to AP anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  network manager does not connect to my AP anymore, tries to
  authenticate and then asks for a password (of a previously connected
  wifi network). Upon entering the right password manually and/or
  verifying the stored password is correct the connection still fails.

  I have not been able to get a concise list of actions that get me connected, 
but a wild mix of:
  rmmod iwlmvm iwlwifi
  modprobe iwlmvm iwlwifi
  killall wpa_supplicant
  iwlist scanning
  (dis-/enabling networking in NWmgr)
  (dis-/enabling wifi in NWmgr) 

  gets me back online

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

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

[Touch-packages] [Bug 1517058] Re: network manager does not connect to AP anymore

[Olli Ries]

HW is a Dell XPS 12 -9Q33

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

Title:
  network manager does not connect to AP anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  network manager does not connect to my AP anymore, tries to
  authenticate and then asks for a password (of a previously connected
  wifi network). Upon entering the right password manually and/or
  verifying the stored password is correct the connection still fails.

  I have not been able to get a concise list of actions that get me connected, 
but a wild mix of:
  rmmod iwlmvm iwlwifi
  modprobe iwlmvm iwlwifi
  killall wpa_supplicant
  iwlist scanning
  (dis-/enabling networking in NWmgr)
  (dis-/enabling wifi in NWmgr) 

  gets me back online

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

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

[Touch-packages] [Bug 1517058] [NEW] network manager does not connect to AP anymore

[Olli Ries]

Public bug reported:

network manager does not connect to my AP anymore, tries to authenticate
and then asks for a password (of a previously connected wifi network).
Upon entering the right password manually and/or verifying the stored
password is correct the connection still fails.

I have not been able to get a concise list of actions that get me connected, 
but a wild mix of:
rmmod iwlmvm iwlwifi
modprobe iwlmvm iwlwifi
killall wpa_supplicant
iwlist scanning
(dis-/enabling networking in NWmgr)
(dis-/enabling wifi in NWmgr) 

gets me back online

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

** Attachment added: "nwmgr & wpasupplicant versions"
   https://bugs.launchpad.net/bugs/1517058/+attachment/4520666/+files/versions

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

Title:
  network manager does not connect to AP anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  network manager does not connect to my AP anymore, tries to
  authenticate and then asks for a password (of a previously connected
  wifi network). Upon entering the right password manually and/or
  verifying the stored password is correct the connection still fails.

  I have not been able to get a concise list of actions that get me connected, 
but a wild mix of:
  rmmod iwlmvm iwlwifi
  modprobe iwlmvm iwlwifi
  killall wpa_supplicant
  iwlist scanning
  (dis-/enabling networking in NWmgr)
  (dis-/enabling wifi in NWmgr) 

  gets me back online

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

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

[Touch-packages] [Bug 1517058] Re: network manager does not connect to AP anymore

[Olli Ries]

data from a series of failed attempts, unloading & loading the drivers

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

Title:
  network manager does not connect to AP anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  network manager does not connect to my AP anymore, tries to
  authenticate and then asks for a password (of a previously connected
  wifi network). Upon entering the right password manually and/or
  verifying the stored password is correct the connection still fails.

  I have not been able to get a concise list of actions that get me connected, 
but a wild mix of:
  rmmod iwlmvm iwlwifi
  modprobe iwlmvm iwlwifi
  killall wpa_supplicant
  iwlist scanning
  (dis-/enabling networking in NWmgr)
  (dis-/enabling wifi in NWmgr) 

  gets me back online

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

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

[Touch-packages] [Bug 1517058] Re: network manager does not connect to AP anymore

[Olli Ries]

** Attachment added: "upstart crash from ~ the same time, not sure if related"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1517058/+attachment/4520669/+files/_sbin_upstart.119.crash

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

Title:
  network manager does not connect to AP anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  network manager does not connect to my AP anymore, tries to
  authenticate and then asks for a password (of a previously connected
  wifi network). Upon entering the right password manually and/or
  verifying the stored password is correct the connection still fails.

  I have not been able to get a concise list of actions that get me connected, 
but a wild mix of:
  rmmod iwlmvm iwlwifi
  modprobe iwlmvm iwlwifi
  killall wpa_supplicant
  iwlist scanning
  (dis-/enabling networking in NWmgr)
  (dis-/enabling wifi in NWmgr) 

  gets me back online

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

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

[Touch-packages] [Bug 1517058] Re: network manager does not connect to AP anymore

[Olli Ries]

uname -a:
Linux minimie 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

lsb-release:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"

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

Title:
  network manager does not connect to AP anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  network manager does not connect to my AP anymore, tries to
  authenticate and then asks for a password (of a previously connected
  wifi network). Upon entering the right password manually and/or
  verifying the stored password is correct the connection still fails.

  I have not been able to get a concise list of actions that get me connected, 
but a wild mix of:
  rmmod iwlmvm iwlwifi
  modprobe iwlmvm iwlwifi
  killall wpa_supplicant
  iwlist scanning
  (dis-/enabling networking in NWmgr)
  (dis-/enabling wifi in NWmgr) 

  gets me back online

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

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

[Touch-packages] [Bug 1517058] Re: network manager does not connect to AP anymore

[Olli Ries]

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1517058/+attachment/4520667/+files/lspci

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

Title:
  network manager does not connect to AP anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  network manager does not connect to my AP anymore, tries to
  authenticate and then asks for a password (of a previously connected
  wifi network). Upon entering the right password manually and/or
  verifying the stored password is correct the connection still fails.

  I have not been able to get a concise list of actions that get me connected, 
but a wild mix of:
  rmmod iwlmvm iwlwifi
  modprobe iwlmvm iwlwifi
  killall wpa_supplicant
  iwlist scanning
  (dis-/enabling networking in NWmgr)
  (dis-/enabling wifi in NWmgr) 

  gets me back online

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

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

[Touch-packages] [Bug 1462664] Re: [Ubuntu Phone] With WIFI = ON the GPS stops

[Olli Ries]

did some housekeeping to get it into the queue

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: location-service (Ubuntu)
 Assignee: (unassigned) => Manuel de la Peña (mandel)

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

Title:
  [Ubuntu Phone] With WIFI = ON the GPS stops

Status in the base for Ubuntu mobile products:
  New
Status in Oxide Webview:
  New
Status in Ubuntu Touch System Settings:
  New
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  Steps: 
  1. Enable WIFI = ON on phone.
  2. Run one of these apps: GPS Navigation, HERE maps, Sensor Status.
  3. Drive.
  4. When you'll be into a WIFI area as a town or city, I'm thinking the WIFI 
will try to search WIFIs and then the GPS will stop, the GPS apps will not 
receive more new positions from the GPS.

  Extra info1: If you had GPS Navigation & Sensor running, both of them
  will not receive new GPS positions from the device. If you restart for
  example GPS Navigation, GPS Navigation will receive new positions, but
  Sensor Status not, until you restart it too.

  Extra info2: When the GPS stops the icon in the status disappears, but
  it you kill and relaunch the app, the icon will appear again.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1377332] Re: [TOPBLOCKER] UI randomly freezes

[Olli Ries]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in the base for Ubuntu mobile products:
  Confirmed
Status in cgmanager package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Opinion
Status in ubuntu-app-launch package in Ubuntu RTM:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  Opinion

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

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

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

[Touch-packages] [Bug 1359337] Re: dialer not remembering current view after lock/unlock

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  dialer not remembering current view after lock/unlock

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in “dialer-app” package in Ubuntu:
  Confirmed
Status in “dialer-app” package in Ubuntu RTM:
  Confirmed

Bug description:
  build 199
  open dialer
  navigate to contacts page or recents page
  lock the phone
  unlock the phone

  Expected results:
  dialer should be on the page you left it on

  Actual results:
  keypad view is always shown

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

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

[Touch-packages] [Bug 1330770] Re: click packages rely upon tls for integrity and authenticity

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  click packages rely upon tls for integrity and authenticity

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Click Package metadata search service:
  Fix Released
Status in Online service used by software center:
  Fix Released
Status in “click” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu:
  Fix Released

Bug description:
  Hello, I just completed a quick review of the click source and the
  unity-scope-click source and behaviours, and found some opportunities
  for improvement.

  Debian, and Ubuntu, rely upon signed repository files with
  cryptographic hashes of packages to provide both integrity and
  authenticity checks for the packages hosted on that repository.

  The click framework and the unity-scope-click discovery and
  installation tool do not use signed repository files, nor do they have
  signatures of any sort on downloaded packages. The only integrity and
  authenticity checks are provided by the use of HTTPS.  The click
  verify command will check files within the archive against MD5sums
  stored inside the archive but the click verify command is not used
  during package installation. (This is suitable for validating
  integrity against accidental changes only.)

  While it appears that unity-scope-click properly uses HTTPS to
  download package metadata and packages, HTTPS alone is insufficient
  for our needs:

  - Someone in a position to create new certificates at any of several
  hundred certificate authorities could create certificates purporting
  to be our update servers. This actual problem has been discovered in
  the wild with several certificate authorities issuing wild-card
  certificates or even certificates with signing authority.

  - X.509 is extremely complicated; TLS is extremely complicated. Flaws
  in both are inevitable.

  - HTTPS prevents the use of caching.

  - HTTPS only 'works' for data-in-motion; it is useless for data-at-
  rest integrity and authenticity checks.

  I have not yet reviewed the tools that application authors will use to
  upload their packages to our distribution servers but note in passing
  that most of these issues are also issues for adding packages to our
  update servers -- packages in flight within our network can be
  corrupted for many reasons, packages on disk can be corrupted for many
  reasons. A signature mechanism can protect against internal network
  faults, storage faults, and provide assurance months or years later
  that an uploaded package was uploaded by someone in control of a
  corresponding private key.

  Thanks

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

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

[Touch-packages] [Bug 1330959] Re: Art in cards with backgrounds are Ubuntu-shaped

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Art in cards with backgrounds are Ubuntu-shaped

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu RTM:
  Triaged

Bug description:
  When a card has its background enabled, the art should not have its
  bottom edge shaped.

  Until the new shape item comes, we should probably use the
  UbuntuShapeForItem component.

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

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

[Touch-packages] [Bug 1343242] Re: Departments break if going to a subdepartment of Store

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Departments break if going to a subdepartment of Store

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu RTM:
  Triaged

Bug description:
  Departments get confused / break when going from a subdepartment of
  Apps (click scope) to same subdepartment of Store via "Get more apps
  like this" orange Store button.

  Steps to reproduce:
  1) Open Apps.
  2) Go to Games department
  3) Click the orange 'Ubuntu store' icon at the bottom (its category title 
should say "Get more apps like this from the Store").
  4) You should be presented with the 'Top Games' category of the store, and 
department tree has only "All" and "Games" subdepartment. It's not possible to 
navigate to the root of the store from it, as UI thinks "All" is the current 
department. Clicking "Games" department, and then "All" restores the correct 
departments menu.

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

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

[Touch-packages] [Bug 1362640] Re: Remove qtwebkit from touch image

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Remove qtwebkit from touch image

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “ubuntu-touch-meta” package in Ubuntu:
  In Progress

Bug description:
  The argument to remove this is based on the following:

  The qtwebkit webview is deprecated for our sdk and we will not be supporting 
it long term
  We are supporting an Oxide/Chromium solution for the Ubuntu.Webview
  This was done largely for security reasons
  The qtwebkit package is large and we would like to reduce image and install 
size 
  We want to discourage app devs from using this api any longer, the review 
tools have indicated this for several months

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

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

[Touch-packages] [Bug 1372948] Re: Keyboard doesn't auto-capitalize 'I'

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Keyboard doesn't auto-capitalize 'I'

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu Keyboard:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  In English 'I' is not auto-capitalized.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-keyboard 0.99.trunk.phablet2+14.10.20140910~rtm-0ubuntu1 
[origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Tue Sep 23 15:44:57 2014
  InstallationDate: Installed on 2014-09-16 (7 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-030205)
  SourcePackage: ubuntu-keyboard
  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/1372948/+subscriptions

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

[Touch-packages] [Bug 1368670] Re: [Dash] Simplify 'Manage Dash' area

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [Dash] Simplify 'Manage Dash' area

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-mediascanner” package in Ubuntu:
  Confirmed
Status in “unity-scopes-shell” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity-scope-mediascanner” source package in Utopic:
  Confirmed
Status in “unity-scopes-shell” source package in Utopic:
  Confirmed
Status in “unity8” source package in Utopic:
  Confirmed
Status in “unity-scopes-shell” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  UX Testing Report: "Replace the current bottom edge screens with the
  simpler "Complete list of Scopes" design."

  New Manage Dash design can be found here:
  
https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/scope-structure-navigation/my-feeds-structure

  Additional UX Testing Report findings addressed by the redesign:

  "Poor discoverability and comprehension of scopes - The use of
  labelings that do not include the word 'scope'/'scopes'"

  "Lack of visual distinctions between apps and scopes in the 'manage
  dash' screen"

  "Undefined relationship between apps and scopes"

  "Search function does not help the discovery of scopes"

  "No dedicated place for adding scopes on the dash"

  "Poor memorability in locating the' manage dash' screen again"

  "The impact of making a scope favourite is unclear"

  "Lack of indication of the nature of the scopes under 'all' tab on
  'manage dash'"

  "Navigation between manage dash and apps scope was difficult"

  "Expect to see categorises instead of content"


  ---
  [EDIT]
  Please refer to the "Dash & Feeds RTM usability fix" for this bug:
  
https://docs.google.com/a/canonical.com/document/d/1LsjdqKDVcFN8Zxb_Oe-Zk1X_DiqviXr8D7-ELt2LEFI/edit?usp=sharing

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

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

[Touch-packages] [Bug 1378417] Re: Icon clipping in notification-renderer

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Icon clipping in notification-renderer

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Discussed with MacSlow in #unity-touch earlier today.

  When indicator-power requests a "low battery" notification, the low
  battery icon gets clipped.

  Here's what it looks like:

  http://i.imgur.com/69hqWlL.jpg

  Here's what is sent to unity-notifications:

  method call sender=:1.104 -> dest=:1.55 serial=18 
path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; 
member=Notify
 string "indicator-power-service"
 uint32 0
 string "battery-020"
 string "Battery Low"
 string "10% charge remaining"
 array [
string "dismiss"
string "OK"
string "settings"
string "Battery settings"
 ]
 array [
dict entry(
   string "x-canonical-non-shaped-icon"
   variant string "true"
)
dict entry(
   string "x-canonical-snap-decisions"
   variant string "true"
)
dict entry(
   string "x-canonical-snap-decisions-timeout"
   variant int32 2147483647
)
 ]
 int32 0

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

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

[Touch-packages] [Bug 1341685] Re: When unconstrained, udm sometimes downloads files to wrong location

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  When unconstrained, udm sometimes downloads files to wrong location

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu Download Manager:
  In Progress
Status in “ubuntu-download-manager” package in Ubuntu:
  In Progress
Status in “ubuntu-download-manager” package in Ubuntu RTM:
  In Progress

Bug description:
  I'm working on making the s-i tests more robust and I've run into an
  odd situation, where udm sometimes stores its downloaded files using
  an incorrect path, and not the one that s-i (which is unconstrained)
  requests.  This only appears to happen when the full s-i test suite is
  run.  When run in isolation, the test succeeds.

  Here's a log of the createDownloadGroup call I'm making:

  createDownloadGroup:
  [Record(url='https://localhost:8943/gpg/blacklist.tar.xz',
  destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz',
  checksum=''),
  Record(url='https://localhost:8943/gpg/blacklist.tar.xz.asc',
  destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz.asc',
  checksum='')]

  url is the source url, destination is the local path to save the file
  in.  This call produces incorrect destination paths in the 'finished'
  signal:

  FINISHED: dbus.Array([dbus.String('/home/barry/.local/share/ubuntu-
  download-manager//usr/lib/telepathy/mission-
  control-5/Downloads/blacklist (20).tar.xz'),
  dbus.String('/home/barry/.local/share/ubuntu-download-
  manager//usr/lib/telepathy/mission-control-5/Downloads/blacklist
  (20).tar.xz.asc')], signature=dbus.Signature('s'))

  Notice the very strange directory udm chooses which is definitely not
  the path requested, and in fact doesn't exist.  This matches the
  observed behavior that after a succesful group download completion
  (i.e. no errors occur), I assert that the requested destination path
  exists, and in the failing test it does not.

  I suspect some state is not getting reset in udm.

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

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

[Touch-packages] [Bug 1378126] Re: Passcode screen misses keypresses

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Passcode screen misses keypresses

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu Keyboard:
  Invalid
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  For some reason the passcode entry screen / lock screen feels very
  laggy when entering my passcode.

  It frequently misses my keypresses, so i end up typing insufficient
  characters. I don't know if the hit area for the numbers is too small
  and I'm mis-hitting or if there is a lag/delay. I'm not typing
  stupendously fast, but pretty quick. Any slower and it feels very
  deliberate, like I'm typing a PIN into an ATM.

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

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

[Touch-packages] [Bug 1368814] Re: Volume slider still available when Silent Mode is on

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Volume slider still available when Silent Mode is on

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Won't Fix
Status in “ubuntu-system-settings” package in Ubuntu:
  Won't Fix

Bug description:
  During usability testing in August, one participant was confused that
  a volume slider was still available after turning on Silent Mode.

  : "Whenever “Silent
  Mode” is on, the volume slider should be insensitive."

  : "As with System Settings,
  whenever Silent Mode is on the volume slider should be insensitive."

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

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

[Touch-packages] [Bug 1381731] Re: [oobe] Shutdown dialog does not appear in welcome wizard

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [oobe] Shutdown dialog does not appear in welcome wizard

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  If you hold down the power button in the wizard, you have to wait
  until the phone hard-shuts off.  But a shutdown dialog should appear
  like it does in the unity8 shell.

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

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

[Touch-packages] [Bug 1378883] Re: [SIM PIN] System Settings missing SIM unlock

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [SIM PIN] System Settings missing SIM unlock

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Network Menu:
  Triaged
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-network” package in Ubuntu:
  Triaged
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged

Bug description:
  Build r91

  1. set up a SIM PIN or make sure the inserted SIM has already a set up SIM 
PIN (reboot device if needed)
  2. after reboot, don't unlock
  3. navigate to System Settings > Security & Privacy > SIM PIN

  What you see: A green tick on the toggle next to the SIM PIN and
  beneath that a "Change PIN..." button

  What you should see: Some way to unlock the SIM without turning off
  the SIM PIN.

  There are three relevant states for a SIM:
  (A) no SIM PIN set
  (B) SIM PIN set, SIM locked
  (C) SIM PIN set, SIM unlocked.

  If a SIM PIN is set, when you start up the phone you have the choice
  to unlock it (switch from B to C) or not (stay on B).

  If you don't unlock it, you can't make or receive calls, send or
  receive SMS, or use cellular data in any app. And you probably can't
  predict ahead of time whether you'll want to do any of those things.

  Currently System Settings only lets you turn the SIM PIN on (A to C)
  or off (C to A), not to unlock it. System Settings should let you do
  this too.

  :
  "Whenever it is locked, at the trailing end should be an 'Unlock…'
  button..."

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

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

[Touch-packages] [Bug 1380662] Re: legacy apps re-set their notification status on reboot

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  legacy apps re-set their notification status on reboot

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  In Progress
Status in “ubuntu-push” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid

Bug description:
  when un-setting the notification defaults for "external drives" this
  setting is respected fine until i reboot my phone, after which the
  setting is auto-enabled again, regardless of what i chose before the
  reboot.

  the same seems to be true for the "system-settings" option in the
  notifications panel. something like gmail or facebook persits fine

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

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

[Touch-packages] [Bug 1387806] Re: toolkit dialogs have wonky padding

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  toolkit dialogs have wonky padding

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu RTM:
  New
Status in “ubuntu-ui-toolkit” package in Ubuntu RTM:
  New

Bug description:
  Ubuntu 14.10 r135

  1. Go to System Settings > "Wi-Fi".
  2. If Wi-Fi is off, turn it on.
  3. Scroll to the bottom of the list and choose "Connect to hidden network".

  What you see: A dialog where the left padding (x1) is less than the
  right padding (x2), and the top padding (y1) is less than the bottom
  padding (y2).

  What you should see: A dialog where the left and right padding are
  equal (x1 = x2), and the top and bottom padding are equal (y1 = y2).

  I don't know whether this is a System Settings bug, a toolkit bug, or
  a combination.

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

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

[Touch-packages] [Bug 1384393] Re: Photos in scope not visible until all loaded

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Photos in scope not visible until all loaded

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Savilerow project:
  Confirmed
Status in “unity-api” package in Ubuntu:
  Invalid
Status in “unity-scopes-api” package in Ubuntu:
  Invalid
Status in “unity-scopes-shell” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  I think this is a generic unity8 issue that is exposed in the My
  Photos scope. This scope displays photos from the photo roll through
  mediascanner.

  Problem:
  When there are many photos, the scope does not display thumbnails for quite a 
while. (It may even be that no photo thumbnails display until all are loaded 
into memory.) This is an awkward user experience because the scope looks like 
nothing is happening for significant periods of time. 

  Expectation:
  Photo thumbnails would display as they arrive. (Perhaps there would be some 
kind of window around what is currently visible in the scope so that as soon as 
photos in the current scroll area, before it by some amount, and after it by 
some amount are in memory, they could display and the user could scroll 
somewhat, with the window moving appropriately.)

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

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

[Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Dash pauses/stutters during scope switching left/right

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Dash pauses/stutters during scope switching left/right.

  Watching the log:   tail -f ~/.cache/upstart/unity8-dash.log

  I can see error messages flood out whenever the dash pauses/stutters
  during left/right swipes:

  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"

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

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

[Touch-packages] [Bug 1385518] Re: Sliding down from backspace key results in continued backspaces

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Sliding down from backspace key results in continued backspaces

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu Keyboard:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu:
  Fix Released
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  Steps to reproduce

  1) Type some text into messaging app

  2) Press backspace key and slide down to return and release

  Expected result

  Backspace stops deleting characters

  Actual result

  Backspace continues to delete until it is tapped again

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

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

[Touch-packages] [Bug 1395075] Re: [Security] Can easily bypass pincode

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [Security] Can easily bypass pincode

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Confirmed

Bug description:
  rtm image 166

  1. reboot the phone
  2. As soon as the greeter is show, try to swipe it away.

  What happens:
  In some attempts we don't see the pincode screen rather 'Scopes' is seen with 
a spinner and there you are unlocked.

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

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

[Touch-packages] [Bug 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  It's too easy to trigger a volume notification when taking a
  screenshot

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Triaged

Bug description:
  On Mako, I'm unable to take a screenshot (Vol up + Vol down) without
  changing the volume, which would be fine if there wasn't a
  notification appearing on the screenshot.

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

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

[Touch-packages] [Bug 1367325] Re: [phone-app] empty state missing in recent view and empty address book

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [phone-app] empty state missing in recent view and empty address book

Status in Address Book App:
  Fix Released
Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “address-book-app” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu RTM:
  New

Bug description:
  1. Open Phone app, make sure you didn't receive or made any calls
  2. Carry out a bottom edge swipe
  3. The list is blank

  Same applies for the Address book app

  
---

  Desired solution:
  Please implement the empty state screen as per design.
  It is confusing for the user not seeing anything in this view.
  Please implement a screen saying "No recent calls" and have a look on the 
empty screen in the messaging app as a reference.

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

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

[Touch-packages] [Bug 1364466] Re: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-service-2.0': double free or corruption (fasttop): ADDR ***

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-
  service-2.0': double free or corruption (fasttop): ADDR ***

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “gstreamer” package in Ubuntu:
  Confirmed
Status in “mediascanner2” package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediascanner2.  This problem was most recently seen with
  version 0.104+14.10.20140825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/354f10fdaba609ee33dd0a2868637ec79c590b56
  and
  https://errors.ubuntu.com/problem/01fcf2789e27c0abf6922c68c02a408b907fab83
  contains more details.

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

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

[Touch-packages] [Bug 1359849] Re: call notifications show "unknown" briefly before showing contact name

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  call notifications show "unknown" briefly before showing contact name

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Telephony Service:
  In Progress
Status in “telephony-service” package in Ubuntu:
  Fix Released
Status in “unity-notifications” package in Ubuntu:
  Invalid
Status in “telephony-service” package in Ubuntu RTM:
  In Progress

Bug description:
  build 203 on krillin

  When receing a call from a contact in your address book that has an
  avatar, the notification is first shown with "Unknown caller" and
  default avatar before switching to the correct name and avatar.

  The name and avatar should be fetched before displaying the
  notification such that when it's shown it's correct right away.

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

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

[Touch-packages] [Bug 1361702] Re: clock-app alarms need to be handled differently from other VTODO events

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  clock-app alarms need to be handled differently from other VTODO
  events

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Date and Time Indicator:
  In Progress
Status in Calendar application for Ubuntu devices:
  Invalid
Status in Ubuntu UI Toolkit:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  In Progress

Bug description:
  When you disable an alarm in the new clock app (with white
  background), it causes the alarm to show up as a calendar event. The
  expected behaviour is to not show up at all.

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

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

[Touch-packages] [Bug 1350891] Re: [Dash] [design] Suru Background should scroll

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [Dash] [design] Suru Background should scroll

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Incomplete
Status in “unity8” package in Ubuntu RTM:
  Incomplete

Bug description:
  On the dash, the Suru paper folds stays fixed at the bottom, while it
  should rather scroll away.

  We should also 'tile' the background, so the paper fold is displayed
  again after scrolling a certain amount of vertical space.

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

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

[Touch-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Pulseaudio should integrate with trust-store

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user ("Foo wants to use
  the microphone. Is this ok? Yes|No"), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

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

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

[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Splash screen is shown as soon as QGuiApplication is instantiated

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Qt integration with the Mir display server:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu RTM:
  Confirmed

Bug description:
  On the phone, a splash screen is shown as soon as QGuiApplication is 
instantiated; however, a QWindow might be created much later, or not be created 
at all.
  We have for example a D-Bus service (ubuntu-system-settings-online-accounts) 
which is a QGuiApplication, but creates QWindows only as client requests 
arrive. In the common case, this works fine because the service is generally 
started when a window needs to be displayed, but we are now preparing for 
implementing trust session support, and that would require either this bug to 
be fixed, or a deeper refactoring of our code.

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

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

[Touch-packages] [Bug 1365673] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlu

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  /usr/lib/arm-linux-
  
gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Qt integration with the Mir display server:
  Confirmed
Status in QT Ubuntu:
  Confirmed
Status in “qtubuntu” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding qtdeclarative-opensource-src.  This problem was most
  recently seen with version 5.3.0-3ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/4618cad07e610ca3c59a3e07c582e963d4780359
  contains more details.

  steps to reproduce:
  run the lrt switch test

  1. open a bunch of apps
  2. swipe the screen to show the app selector
  3. pick an app at random
  4. swipe the screen again to show the app selector
  5. pick an app at random
  6. repeat steps 2-5 until crash shows in /var/log

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

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

[Touch-packages] [Bug 1368680] Re: [design] [Dash] pagination graphic should remain static when swiping between favourites.

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [design] [Dash] pagination graphic should remain static when swiping
  between favourites.

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu RTM:
  Confirmed

Bug description:
  Pagination graphic should remain fixed in place when swiping between 
favourites contained within the dash.
  'Dot' used to communicate which favourite is currently being viewed should be 
more visible (switch colour from Dark Grey to Orange colour used for 
highlights, etc):

  See here for more info on dash pagination (page 10):
  
https://docs.google.com/a/canonical.com/document/d/1LsjdqKDVcFN8Zxb_Oe-Zk1X_DiqviXr8D7-ELt2LEFI/edit?usp=sharing

  
  UX Testing Report finding & recommendation:

  "No incentive to discover scopes beyond the apps scope.  Lack of
  strong visual cues to hint swiping from the apps scope to discover
  more scopes on the right."

  "In the SURU divider pagination pattern (as currently used by the
  Dash), change the selected colour from orange to white."

  "When the Scopes slide, the SURU divider portion of the screen should
  not slide (it should remain static).  The state of the 'dot'
  pagination pattern should of course change. Keeping the SURU divider
  static should make the change to the pagination pattern more
  noticeable."

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

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

[Touch-packages] [Bug 1374082] Re: no API to unlock a specific sim

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  no API to unlock a specific sim

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Network Menu:
  Triaged
Status in “indicator-network” package in Ubuntu:
  Triaged
Status in “indicator-network” source package in Utopic:
  Triaged
Status in “indicator-network” source package in Vivid:
  Triaged
Status in “indicator-network” package in Ubuntu RTM:
  Triaged

Bug description:
  In dialer-app on dual sim phones users will be given an option to unlock a 
specific modem.
  The current api only supports unlocking all modems at once: 
UnlockAllModems(). We need a way to invoke the unlock screen to a specific 
modem, like UnlockModem(objectPath).

  clients:
  https://bugs.launchpad.net/messaging-app/+bug/1371661

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

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

[Touch-packages] [Bug 1378048] Re: Make music controls work in the sound indicator

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Make music controls work in the sound indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Incomplete
Status in “media-hub” package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Play an album in the music player
  2. Pull down sound indicator
  3. Click forward button

  Observed: the music does not advance
  Expected: the music advances

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

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

[Touch-packages] [Bug 1372061] Re: SMS notification: time format not translatable

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  SMS notification: time format not translatable

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu Translations:
  Triaged
Status in “telephony-service” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Triaged

Bug description:
  See the attached screenshot. The time for the notification seems to be
  hardcoded to "hh:mm - mm, d". This works well for the US, but it's not
  a format that is used in all other countries. In Spain, for example,
  the date would rather be "d mm".

  The time format needs to be marked for translation.

  Not sure from which project the notifications come from, for some
  reason I seem to remember they were moved to u-s-s, but if it's the
  wrong project/package, please reassign. Thanks!

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

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

[Touch-packages] [Bug 1384422] Re: [SDK] text selection popup menu gets obscured by finger

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [SDK] text selection popup menu gets obscured by finger

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  krillin rtm 122

  The popup menu should be displayed higher up than it currently is as
  it's getting obscured by your finger that is doing the press and hold

  Steps to reproduce:
  - type some text in the messaging app
  - double tap a word
  - long press on the word

  Expected results:
  - popup menu should be displayed well above the selection so it's not blocked 
by finger

  Actual results:
  - popup menu is sometimes not displayed at all, but when it is it's partially 
obscured by finger and displayed too low

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

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

[Touch-packages] [Bug 1390098] Re: Active call panel incorrectly displayed when recieving a call

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Active call panel incorrectly displayed when recieving a call

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in “dialer-app” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Invalid
Status in “dialer-app” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  Invalid

Bug description:
  rtm build 140 on krillin

  Steps to reproduce:
  - open dialer
  - call the phone
  - answer the call

  Expected results:
  - dialer live call view should be displayed
  - no Active call panel visible

  Actual results:
  - dialer live call view displayed
  - Active call panel is briefly displayed and then hidden

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

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

[Touch-packages] [Bug 1379836] Re: dialer and messaging app show unlocked pin as locked

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  dialer and messaging app show unlocked pin as locked

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Telepathy Ofono:
  In Progress
Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Triaged
Status in “telepathy-ofono” package in Ubuntu:
  Fix Released
Status in “telepathy-ofono” package in Ubuntu RTM:
  Confirmed

Bug description:
  Ubuntu System Settings and ofono say it's unlocked but trying to use
  the dialer and messaging app is blocked by thinking the PIN is locked.

  $ system-image-cli -i
  current build number: 81
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-10 15:33:48
  version version: 81
  version ubuntu: 20141010.1
  version device: 20140929.1
  version custom: mako-0.7

  $ phablet-shell 
  /home/sergiusens/.ssh/known_hosts updated.
  Original contents retained as /home/sergiusens/.ssh/known_hosts.old
  Warning: Permanently added '[localhost]:' (RSA) to the list of known 
hosts.
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako 
armv7l)

   * Documentation:  https://help.ubuntu.com/
  Last login: Fri Oct 10 15:37:40 2014 from localhost.localdomain
  phablet@ubuntu-phablet:~$ lis^C
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems 
  [ /ril_0 ]
  Features = gprs ussd net sms rat sim 
  Model = Fake Modem Model
  Powered = 1
  Emergency = 0
  Online = 1
  Interfaces = org.ofono.ConnectionManager org.ofono.CallBarring 
org.ofono.CallSettings org.ofono.SupplementaryServices 
org.ofono.NetworkRegistration org.ofono.CallForwarding org.ofono.SmartMessaging 
org.ofono.PushNotification org.ofono.MessageManager org.ofono.NetworkTime 
org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager 
org.ofono.CallVolume org.ofono.VoiceCallManager 
  Revision = M9615A-CEFWMAZM-2.0.1701.03
  Type = hardware
  Manufacturer = Fake Manufacturer
  Serial = 355136052657866
  Lockdown = 0
  [ org.ofono.ConnectionManager ]
  Bearer = hspa
  RoamingAllowed = 0
  Suspended = 0
  Powered = 1
  Attached = 1
  [ org.ofono.CallBarring ]
  VoiceIncoming = disabled
  VoiceOutgoing = disabled
  [ org.ofono.CallSettings ]
  CallingLineRestriction = off
  HideCallerId = default
  ConnectedLinePresentation = unknown
  ConnectedLineRestriction = unknown
  CallingLinePresentation = enabled
  CallingNamePresentation = unknown
  CalledLinePresentation = disabled
  VoiceCallWaiting = enabled
  [ org.ofono.SupplementaryServices ]
  State = idle
  [ org.ofono.NetworkRegistration ]
  Mode = auto
  Name = Personal
  LocationAreaCode = 394
  Status = registered
  CellId = 14122637
  MobileCountryCode = 722
  Technology = umts
  Strength = 61
  MobileNetworkCode = 34
  [ org.ofono.CallForwarding ]
  VoiceNotReachable = +541151009255
  VoiceNoReplyTimeout = 25
  VoiceUnconditional = 
  VoiceNoReply = +541151009255
  ForwardingFlagOnSim = 0
  VoiceBusy = +541151009255
  [ org.ofono.SmartMessaging ]
  [ org.ofono.PushNotification ]
  [ org.ofono.MessageManager ]
  Alphabet = default
  UseDeliveryReports = 0
  ServiceCenterAddress = +541151740055
  Bearer = cs-preferred
  [ org.ofono.NetworkTime ]
  [ org.ofono.MessageWaiting ]
  VoicemailWaiting = 0
  VoicemailMailboxNumber = *555
  VoicemailMessageCount = 0
  [ org.ofono.RadioSettings ]
  TechnologyPreference = umts
  ModemTechnologies = gsm umts 
  FastDormancy = 0
  [ org.ofono.SimManager ]
  CardIdentifier = 89543421113404033941
  ServiceNumbers = [Llam. a su Cargo] = '11' [Club Personal] = 
'*2582' [Personal] = '+810' [At. Clientes] = '*111' 
  Retries = 
  FixedDialing = 0
  SubscriberIdentity = 722341240403394
  MobileCountryCode = 722
  BarredDialing = 0
  PinRequired = none
  LockedPins = 
  SubscriberNumbers = 
  Present = 1
  PreferredLanguages = es en pt it 
  MobileNetworkCode = 34
  [ org.ofono.CallVolume ]
   

[Touch-packages] [Bug 1387231] Re: [regression][clock] alarm still rings once it's been disabled or deleted

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [regression][clock] alarm still rings once it's been disabled or
  deleted

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  In Progress

Bug description:
  (r135)

  Steps to reproduce:

  1. Create a single type alarm to ring in the next 5 minutes.
  2. Wait for the alarm to ring.
  3. After dismissing the alarm, delete it from the clock app.

  Actual behaviour:

  Once the alarm's been deleted, it still rings!

  Expected behaviour:

  Once you delete the alarm, this shouldn't ring anymore.

  

  Mako, Image #5 ubuntu rtm,

  Steps to reproduce:

  1. Create an alarm to ring in the next 5 minutes.
  2. Disable the alarm after it is created.

  Actual Behaviour:

  Alarm still rings!

  Expected Behaviour:

  Once you disable an alarm, it shouldn't ring anymore.

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

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

[Touch-packages] [Bug 1380766] Re: revert listitem dividers to previous (no margins)

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  revert listitem dividers to previous (no margins)

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress

Bug description:
  2gu margin was added to the left and right of listitem dividers.

  However this is causing issues with a large number of apps. For RTM
  let's revert back to previous (no left/right margins on listitem
  dividers) and after that we can explore the issues again.

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

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

[Touch-packages] [Bug 1378006] Re: [phone-app] call controls and header in active call are not as per design

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [phone-app] call controls and header in active call are not as per
  design

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu RTM:
  New

Bug description:
  Build r 84
  The current active call screen doesn't show the correct call controls and 
header, as per design.

  The header shouldn't have the contacts icon in the top right corner.
  The "add to call" icon is missing in the call controls. It seems as well, 
that the SURU icon theme is not applied.
  Please see attached wireframe for reference.

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

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

[Touch-packages] [Bug 1382109] Re: Events view should be shown on import

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Events view should be shown on import

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Gallery App:
  In Progress
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “gallery-app” package in Ubuntu RTM:
  In Progress

Bug description:
  If a photo is imported via the content-hub, we should always make sure
  to display the Events view as the photo will show up by default there.

  Currenty if the gallery is open to a specific photo or album, after
  the import occurs we don't update the view so user has no idea where
  the imported picture is.

  Would be nice to directly open the imported picture but this won't
  work as we might get multiple import events in a row from content-hub
  in the case where the user "Dimissed" the open dialog multiple times.
  Next time gallery-app launched or displayed it will be delivered
  multiple events so we would not know which to open.

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

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

[Touch-packages] [Bug 1376500] Re: thumbnails in metadata generated incorrectly

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  thumbnails in metadata generated incorrectly

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “libhybris” package in Ubuntu:
  Fix Released
Status in “qtubuntu-camera” package in Ubuntu:
  Fix Released
Status in “thumbnailer” package in Ubuntu:
  Fix Released
Status in “qtubuntu-camera” package in Ubuntu RTM:
  In Progress
Status in “thumbnailer” package in Ubuntu RTM:
  In Progress

Bug description:
  build 76 rtm-proposed on krillin

  Take a picture with camera-app
  swipe to the right to display it
  it looks squashed and like it's being displayed at the wrong aspect ratio
  open the gallery-app and view the photo and it looks equally bad
  share the photo to messaging-app, and the preview of the photo is black
  copy the photo to your desktop and open there and the photo looks fine

  these are all new regressions, not sure what layer it's in bug
  guessing a low layer as gallery, camera and messaging-app have not
  changed in this regard

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

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

[Touch-packages] [Bug 1381583] Re: imported pictures should show in Event for today

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  imported pictures should show in Event for today

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Gallery App:
  In Progress
Status in Ubuntu UX bugs:
  New
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “gallery-app” package in Ubuntu RTM:
  Fix Released

Bug description:
  When pictures are imported into the gallery, via content-hub, we
  should always display them in the Event for the current day. Right
  now, the picture is played in the Event that corresponds to the
  metadata creation date which is very confusing because after the
  picture is imported you can't find it easily.

  Arthur and I discussed modifiying one of the standard exif tags (like
  DateTime, but don't modify CreationDate) with the current date of
  import as the gallery already sorts by a series of tags. Another
  solution would be to add a custom tag like (importDate) and change the
  sort to use that if it exists before falling back to other tags.

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

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

[Touch-packages] [Bug 1389514] Re: open photo from scope fails on first try

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  open photo from scope fails on first try

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Gallery App:
  In Progress
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “gallery-app” package in Ubuntu RTM:
  New

Bug description:
  The Photos scope and gallery app support a mechanism where a photo can
  be opened directly in the gallery by tapping 'open' on it in the
  photos scope.  However, this appears to fail on the first try if
  Gallery hasn't been run before.

  Steps to reproduce this:
  1. Flash the phone to get a fresh install.
  2. Take some photos in the camera app.
  3. Navigate to those photos in the Photos scope.
  4. Select a photo and tap 'open'.

  Expected results: Selected photo opens in the gallery app.

  Actual results: Gallery app opens and shows the 'Events' view, but does not 
open the chosen photo.
  On second attempt, the expected results happen.

  I suspect that the gallery app may be getting stuck on indexing and
  thumbnailing the first time, and once that is done things work as
  expected.

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

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

[Touch-packages] [Bug 1392401] Re: Bottom edge tip should disappear when interacting with the UI

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Bottom edge tip should disappear when interacting with the UI

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  In Progress
Status in “dialer-app” package in Ubuntu RTM:
  New

Bug description:
  The bottom edge tip should be hidden as soon as the user starts to
  interact with the other UI elements.

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

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

[Touch-packages] [Bug 1387763] Re: deleting Google contacts not working reliably

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  deleting Google contacts not working reliably

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “address-book-service” package in Ubuntu:
  Fix Released
Status in “address-book-service” package in Ubuntu RTM:
  In Progress

Bug description:
  krillin build 132 on rtm

  Steps to repdouce:

  - create 2 google accounts
  - enable contact syncing on 1 of the accounts
  - let the sync happen and open addresss book to verify the contacts are 
displayed
  - go back to system settings for accounts
  - delete the google account associated with the contact sync
  - when prompted, say "No" to keep contact data
  - go back to address book

  Expected results:
  - all the contacts should be gone from address book

  Actual results:
  - all the contacts remain in the address book

  I've seen this work sometimes and fail quite often, so not sure what
  is going on. But it's pretty easy to reproduce.

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

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

[Touch-packages] [Bug 1389611] Re: "swipe to the photo roll" hint should wrap rather than elide

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  "swipe to the photo roll" hint should wrap rather than elide

Status in Camera App:
  In Progress
Status in the base for Ubuntu mobile products:
  Confirmed
Status in “camera-app” package in Ubuntu:
  In Progress
Status in “camera-app” package in Ubuntu RTM:
  New

Bug description:
  Using rtm 142 (with updated translations done manually from
  launchpad), the new "swipe to the photo roll" hint is eliding, but it
  leads to the text difficult to understand in some locales...

  Screenshot from a french example attached to show the issue

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

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

[Touch-packages] [Bug 1379386] Re: [emergency call] + [phone-app] remove SIM card naming from SURU divider in emergency dialer mode

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [emergency call] + [phone-app] remove SIM card naming from SURU
  divider in emergency dialer mode

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu RTM:
  New

Bug description:
  Build r93
  Make sure your device has both cards inserted

  Steps to reproduce: 
  1. make sure your device has a passcode/passphrase lock
  2. unlock device via HK button, swipe away the greeter
  3. you should see then unlocking panel, tap emergency call on the bottom

  Actual result: the dialer view shows SIM card names in the header sections 
(suru divider)
  Expected result: dialer should NOT show any SIM names in the header sections

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

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

[Touch-packages] [Bug 1375890] Re: [messaging-app] + [phone-app] different time formats and font strenghts

[Olli Ries]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [messaging-app] + [phone-app] different time formats and font
  strenghts

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Messaging App:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Fix Released
Status in “messaging-app” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu RTM:
  New
Status in “messaging-app” package in Ubuntu RTM:
  In Progress

Bug description:
  Steps to reproduce:
  1. Open messaging app, stay in the main view
  2. Open phone-app, carry out a bottom edge swipe to access your recent

  In comparison, both apps are using a different font size, font strength and 
time format. Is the time format set by system settings?
  Desired solution: 
  - phone app - there shouldn't be a space between the time stamp and "am" or 
"pm"  -> "07:34pm"
  - messaging app - apply the same visual treatment for the time stamp as in 
the phone app

  Please see attachments for reference.

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

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

[Touch-packages] [Bug 1395748] Re: Crash going back twice while loading a page

[Olli Ries]

I can reproduce it when you quickly tap twice / multiple times

It survives when you tap multiple times, but less rapidly (still << 1s).

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

Title:
  Crash going back twice while loading a page

Status in Web Browser App:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  In Progress
Status in “webbrowser-app” package in Ubuntu RTM:
  In Progress

Bug description:
  Test case.
  - Go to start.ubuntu.com
  - After it loads, go to slashdot.org
  - After it loads, go to linux.com
  - While it is loading, tap to back button twice to go back to start.ubuntu.com

  Expected result.
  - Browser displays start.ubuntu.com

  Actual result.
  - Crash.

  current build number: 118
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09.es-proposed

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

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

[Touch-packages] [Bug 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot

[Olli Ries]

** Changed in: unity8 (Ubuntu)
   Importance: High => Critical

** Tags added: ota-1 rtm14

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

Title:
  It's too easy to trigger a volume notification when taking a
  screenshot

Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  On Mako, I'm unable to take a screenshot (Vol up + Vol down) without
  changing the volume, which would be fine if there wasn't a
  notification appearing on the screenshot.

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

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

[Touch-packages] [Bug 1389514] Re: open photo from scope fails on first try

[Olli Ries]

** Tags removed: ota-1
** Tags added: touch-2014-11-20

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

Title:
  open photo from scope fails on first try

Status in Gallery App:
  In Progress
Status in “gallery-app” package in Ubuntu:
  In Progress
Status in “gallery-app” package in Ubuntu RTM:
  New

Bug description:
  The Photos scope and gallery app support a mechanism where a photo can
  be opened directly in the gallery by tapping 'open' on it in the
  photos scope.  However, this appears to fail on the first try if
  Gallery hasn't been run before.

  Steps to reproduce this:
  1. Flash the phone to get a fresh install.
  2. Take some photos in the camera app.
  3. Navigate to those photos in the Photos scope.
  4. Select a photo and tap 'open'.

  Expected results: Selected photo opens in the gallery app.

  Actual results: Gallery app opens and shows the 'Events' view, but does not 
open the chosen photo.
  On second attempt, the expected results happen.

  I suspect that the gallery app may be getting stuck on indexing and
  thumbnailing the first time, and once that is done things work as
  expected.

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

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

[Touch-packages] [Bug 1382109] Re: Events view should be shown on import

[Olli Ries]

** Tags added: ota-1

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

Title:
  Events view should be shown on import

Status in Gallery App:
  In Progress
Status in “gallery-app” package in Ubuntu:
  In Progress
Status in “gallery-app” package in Ubuntu RTM:
  In Progress

Bug description:
  If a photo is imported via the content-hub, we should always make sure
  to display the Events view as the photo will show up by default there.

  Currenty if the gallery is open to a specific photo or album, after
  the import occurs we don't update the view so user has no idea where
  the imported picture is.

  Would be nice to directly open the imported picture but this won't
  work as we might get multiple import events in a row from content-hub
  in the case where the user "Dimissed" the open dialog multiple times.
  Next time gallery-app launched or displayed it will be delivered
  multiple events so we would not know which to open.

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

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

[Touch-packages] [Bug 1377332] Re: [TOPBLOCKER] UI randomly freezes

[Olli Ries]

** Changed in: unity8 (Ubuntu)
   Importance: High => Critical

** Changed in: ubuntu-app-launch (Ubuntu)
   Importance: High => Critical

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in “cgmanager” package in Ubuntu:
  Incomplete
Status in “ubuntu-app-launch” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “ubuntu-app-launch” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

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

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

[Touch-packages] [Bug 1387708] Re: [TOPBLOCKER] Location services not getting location

[Olli Ries]

** Changed in: location-service (Ubuntu-rtm 14.09)
   Status: In Progress => Fix Released

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

Title:
  [TOPBLOCKER] Location services not getting location

Status in Location Service:
  New
Status in “location-service” package in Ubuntu:
  In Progress
Status in “location-service” package in Ubuntu RTM:
  Fix Released
Status in “location-service” source package in 14.09:
  Fix Released

Bug description:
  Failing to get location fix from application.
  Neither network based nor gps location works.
  Bug has now been seen on 3 phones with and without SIM installed.
  HERE service seems to be running, but no reasonable location is reported.
  GPS is failing to get fix, tested with phone placed for 2 hours outside.

  On two of those phones location was working fine, but with OTA update to ~135 
stopped working.
  hard to guess working image but somewhere around 129~131

  
  Problem is now reproducible on RTM release 137

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions

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

[Touch-packages] [Bug 1380848] Re: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets

[Olli Ries]

** Changed in: dbus-cpp (Ubuntu)
   Status: New => Incomplete

** Changed in: dbus-cpp (Ubuntu)
   Status: Incomplete => In Progress

** Summary changed:

- [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets
+ Apps and services use large amount of CPU after unity8 resets

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

Title:
  Apps and services use large amount of CPU after unity8 resets

Status in Media Hub:
  In Progress
Status in “dbus-cpp” package in Ubuntu:
  In Progress
Status in “media-hub” package in Ubuntu:
  Fix Released
Status in “media-hub” package in Ubuntu RTM:
  Fix Released

Bug description:
  I noticed that media-hub-service can get into a state where it uses a
  large amount of CPU.

  Steps to reproduce
  1) Start music-app
  2) Play music
  3) Pause music
  4) Close the music-app
  5) $ pkill unity8 (to emulate unity crashing a resetting)

  Notice that media-hub-service is now using a large amount of CPU, note
  this [0] is the media-hub.log at the time.

  The device has to be reset to get the CPU usage back to normal.

  0 - http://pastebin.ubuntu.com/8553411/

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions

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

[Touch-packages] [Bug 1391498] Re: [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header with the word "Apps"

[Olli Ries]

** Changed in: unity-scope-click (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-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1391498

Title:
  [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the
  header with the word "Apps"

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  In Progress

Bug description:
  [Dash] In the app scope, replace the Ubuntu icon in the header with
  the word "Apps"

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

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

[Touch-packages] [Bug 1391498] Re: [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header with the word "Apps"

[Olli Ries]

** Tags removed: touch-2014-11-06
** Tags added: touch-2014-11-13

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

Title:
  [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the
  header with the word "Apps"

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  In Progress

Bug description:
  [Dash] In the app scope, replace the Ubuntu icon in the header with
  the word "Apps"

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

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

[Touch-packages] [Bug 1391498] Re: [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header with the word "Apps"

[Olli Ries]

** Changed in: unity-scope-click (Ubuntu)
 Assignee: (unassigned) => Thomas Strehl (strehl-t)

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

Title:
  [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the
  header with the word "Apps"

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  [Dash] In the app scope, replace the Ubuntu icon in the header with
  the word "Apps"

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

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

[Touch-packages] [Bug 1377332] Re: [TOPBLOCKER] UI randomly freezes

[Olli Ries]

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

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in “cgmanager” package in Ubuntu:
  Incomplete
Status in “ubuntu-app-launch” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “ubuntu-app-launch” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

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

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

[Touch-packages] [Bug 1391498] Re: [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header with the word "Apps"

[Olli Ries]

** Tags removed: ota-1
** Tags added: touch-2014-11-06

** Tags removed: touch-2014-11-06
** Tags added: touch-0

** Tags removed: touch-0
** Tags added: touch-2014-11-06

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

Title:
  [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the
  header with the word "Apps"

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  [Dash] In the app scope, replace the Ubuntu icon in the header with
  the word "Apps"

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

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

[Touch-packages] [Bug 1377332] Re: [TOPBLOCKER] UI randomly freezes

[Olli Ries]

** Tags removed: ota-1
** Tags added: touch-2014-11-06

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in “ubuntu-app-launch” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “ubuntu-app-launch” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

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

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

[Touch-packages] [Bug 1391498] Re: [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header with the word "Apps"

[Olli Ries]

** Summary changed:

- [Dash] In the app scope, replace the Ubuntu icon in the header with the word 
"Apps"
+ [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header 
with the word "Apps"

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

Title:
  [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the
  header with the word "Apps"

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  [Dash] In the app scope, replace the Ubuntu icon in the header with
  the word "Apps"

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

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

[Touch-packages] [Bug 1391324] Re: can't interact with call after previous call hangs up

[Olli Ries]

** Changed in: dialer-app (Ubuntu RTM)
   Importance: Undecided => Critical

** Tags added: touch-2014-11-06

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

Title:
  can't interact with call after previous call hangs up

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in “dialer-app” package in Ubuntu:
  New
Status in “dialer-app” package in Ubuntu RTM:
  New

Bug description:
  build 152 on rtm

  I can get the dialer into a state where it's frozen and you can't
  interact with it anymore

  Steps to reproduce
  - receive a call on Ubuntu phone
  - switch away to another app, like browser
  - hang up from the remote side
  - call the Ubuntu phone again
  - answer the call

  Expected results:
  - the dialer-app live call view is shown, can interact as normal

  Actual results:
  - the dialer-app shows the "Call Ended" screen from the previous call
  - the dialer is unresponsive, the hang up button does nothing
  - you have to kill and restart the app to recover

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

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

[Touch-packages] [Bug 1377332] Re: UI randomly freezes

[Olli Ries]

** Changed in: unity8 (Ubuntu RTM)
   Importance: High => Critical

** Changed in: ubuntu-app-launch (Ubuntu RTM)
   Importance: Undecided => Critical

** Summary changed:

- UI randomly freezes
+ [TOPBLOCKER] UI randomly freezes

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in “ubuntu-app-launch” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  In Progress
Status in “ubuntu-app-launch” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

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

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

[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)

[Olli Ries]

** Tags added: touch-2014-11-06

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

Title:
  Often fails to connect to Pulseaudio and unity-notifications (results
  in missing volume notifications and improper volume control)

Status in Sound Menu:
  Triaged
Status in “indicator-sound” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “indicator-sound” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Often after boot indicator-sound fails to connect to Pulseaudio and to
  unity-notifications using libnotify. Therefore, volume notifications
  aren't shown and changes to the volume role go unnoticed, which then
  results in improper volume control.

  As already mentioned in the original bug description, running "restart
  indicator-sound" resolves the issue.

  Original description:

  Happens often after phone boot where changing volume by touch or by
  phone buttons. Volume correctly changes, but the
  org.freedesktop.Notifications popup isn't displayed.

  The problem seems fixes itself if you run "restart indicator-sound",
  so maybe there's an issue with i-sound and unity-notifications
  starting at the same time, with the former querying the latter's
  capabilities before it's ready for business?

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

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

[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)

[Olli Ries]

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

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

Title:
  Often fails to connect to Pulseaudio and unity-notifications (results
  in missing volume notifications and improper volume control)

Status in Sound Menu:
  Triaged
Status in “indicator-sound” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “indicator-sound” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Often after boot indicator-sound fails to connect to Pulseaudio and to
  unity-notifications using libnotify. Therefore, volume notifications
  aren't shown and changes to the volume role go unnoticed, which then
  results in improper volume control.

  As already mentioned in the original bug description, running "restart
  indicator-sound" resolves the issue.

  Original description:

  Happens often after phone boot where changing volume by touch or by
  phone buttons. Volume correctly changes, but the
  org.freedesktop.Notifications popup isn't displayed.

  The problem seems fixes itself if you run "restart indicator-sound",
  so maybe there's an issue with i-sound and unity-notifications
  starting at the same time, with the former querying the latter's
  capabilities before it's ready for business?

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

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

[Touch-packages] [Bug 1384749] Re: Detected X, Y coordinates for touch event on text field is off

[Olli Ries]

** Summary changed:

- [TOPBLOCKER] Detected X,Y coordinates for touch event on text field is off
+ Detected X,Y coordinates for touch event on text field is off

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

Title:
  Detected X,Y coordinates for touch event on text field is off

Status in Ubuntu UI Toolkit:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress

Bug description:
  Tapping on a word in a text input seems to select the word below,
  rather than the one I intended to select

  The Y seems to be lower by approx. 1 GU

  Reproduce by
  - Go to messages and tap on message filed
  - Enter 4 rows of content
  - Tap on a word in the second row
  - The word below is often selected

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

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

[Touch-packages] [Bug 1387216] Re: [Dash] Remove Header's Suru Background

[Olli Ries]

** Tags removed: ota-1
** Tags added: touch-2014-11-06

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

Title:
  [Dash] Remove Header's Suru Background

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  Fix Released
Status in “unity-scope-mediascanner” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Invalid
Status in “unity-scope-click” package in Ubuntu RTM:
  Triaged

Bug description:
  The origami pattern on the header is not working as expected from a
  design standpoint and should be removed and reverted to the plain
  header.

  --
  Desired resolution:
  - revert the single asset swap that introduced the new header background that 
does not work.

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

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

[Touch-packages] [Bug 1381930] Re: [TOPBLOCKER] 7digital previews do not play in the scope

[Olli Ries]

marking the remaining Ubuntu task as high to get off rtm list

** Changed in: unity-scopes-api (Ubuntu)
   Importance: Critical => High

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

Title:
  [TOPBLOCKER] 7digital previews do not play in the scope

Status in “qtbase-opensource-src” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu:
  Fix Released
Status in “unity-scope-mediascanner” package in Ubuntu:
  Invalid
Status in “unity-scopes-api” package in Ubuntu:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu RTM:
  Fix Released
Status in “unity-scopes-api” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Invalid

Bug description:
  Steps to reproduce:

  1. Navigate to the music scope
  2. In the section 'New albums from 7digital' click on any album
  3. Press the play button on one of the track previews

  Expected result:

  The preview plays

  Actual result:

  No preview plays

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: armhf
  Date: Thu Oct 16 08:11:12 2014
  InstallationDate: Installed on 2014-10-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141016-010328)
  SourcePackage: unity-scope-mediascanner
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384749] Re: [TOPBLOCKER] Detected X, Y coordinates for touch event on text field is off

[Olli Ries]

reducing to High as per comment #6 and discussion on 11/7

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Critical => High

** Changed in: ubuntu-ui-toolkit
   Importance: Critical => High

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

Title:
  [TOPBLOCKER] Detected X,Y coordinates for touch event on text field is
  off

Status in Ubuntu UI Toolkit:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress

Bug description:
  Tapping on a word in a text input seems to select the word below,
  rather than the one I intended to select

  The Y seems to be lower by approx. 1 GU

  Reproduce by
  - Go to messages and tap on message filed
  - Enter 4 rows of content
  - Tap on a word in the second row
  - The word below is often selected

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

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

[Touch-packages] [Bug 1388594] Re: [TOPBLOCKER] dialer app can thrash cpu after caller hangs up on you

[Olli Ries]

** Changed in: dialer-app (Ubuntu)
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  [TOPBLOCKER] dialer app can thrash cpu after caller hangs up on you

Status in “dialer-app” package in Ubuntu:
  Confirmed

Bug description:
  summary
  dialer app can thrash cpu after caller hangs up on you

  steps:
  1. answer call from someone using snap decision bubble
  2. talk for a while
  3. let the caller hang up on you

  expected results:
  dialer app isn't using 100% cpu after call

  actual results 
  dialer app continues to thrash cpu

  snap shot from top 5 minutes after call
PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   7412 phablet   20   0  253352  50876  25296 S 100.0  5.2  11:41.13 
dialer-app  
751 message+  20   09480   6680756 S   1.3  0.7   4:03.64 
dbus-daemon

  version info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 140
  version_detail: 
ubuntu=20141031.1,device=20141028-3ca60be,custom=1414598646,version=140

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

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

[Touch-packages] [Bug 1378576] Re: /usr/bin/mtp-server:11:boost::asio::detail::epoll_reactor::run:do_run_one:boost::asio::detail::task_io_service::run:run:core::dbus::asio::Executor::run

[Olli Ries]

** Tags removed: ota-1
** Tags added: touch-2014-11-06

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

Title:
  /usr/bin/mtp-
  
server:11:boost::asio::detail::epoll_reactor::run:do_run_one:boost::asio::detail::task_io_service::run:run:core::dbus::asio::Executor::run

Status in “mtp” package in Ubuntu:
  Fix Released
Status in “mtp” package in Ubuntu RTM:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mtp.  This problem was most recently seen with version
  0.0.4+14.10.20140909-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/87eeef0f5fc222be4eec263453315ce37235a27d
  contains more details.

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

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

[Touch-packages] [Bug 1358343] Re: [TOPBLOCKER] too easy to answer a call by accident

[Olli Ries]

set the Ubuntu Tasks to High to get it of the RTM list

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

Title:
  [TOPBLOCKER] too easy to answer a call by accident

Status in Telephony Service:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Invalid
Status in “telephony-service” package in Ubuntu:
  Confirmed
Status in “unity-notifications” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “telephony-service” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  If you put the phone in your pocket with locked screen and you receive
  a call is too easy to answer or reject that by mistake. Or pressing
  the screen while trying to get the phone or the call can be answered
  without you noticed by your pocket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1358343/+subscriptions

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

[Touch-packages] [Bug 1358343] Re: [TOPBLOCKER] too easy to answer a call by accident

[Olli Ries]

** Changed in: telephony-service (Ubuntu)
   Importance: Critical => High

** Changed in: telephony-service
   Importance: Critical => High

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

Title:
  [TOPBLOCKER] too easy to answer a call by accident

Status in Telephony Service:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Invalid
Status in “telephony-service” package in Ubuntu:
  Confirmed
Status in “unity-notifications” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “telephony-service” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  If you put the phone in your pocket with locked screen and you receive
  a call is too easy to answer or reject that by mistake. Or pressing
  the screen while trying to get the phone or the call can be answered
  without you noticed by your pocket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1358343/+subscriptions

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

[Touch-packages] [Bug 1354068] Re: /usr/bin/unity8:11:std::function:SlotWrapper:core::Signal:core::dbus::Signal:operator

[Olli Ries]

did this one land?

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

Title:
  
/usr/bin/unity8:11:std::function:SlotWrapper:core::Signal:core::dbus::Signal:operator

Status in Mir:
  Invalid
Status in “dbus-cpp” package in Ubuntu:
  Fix Committed
Status in “media-player” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.00+14.10.20140805-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/8c88c781c702b88274b020e223d66d63e2d34a33
  contains more details.

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

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

[Touch-packages] [Bug 1355095] Re: mediaplayer hangs on fast-forward

[Olli Ries]

** Changed in: media-hub
   Status: Fix Committed => Fix Released

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

Title:
  mediaplayer hangs on fast-forward

Status in Media Hub:
  Fix Released
Status in Media Player App:
  New
Status in “mediaplayer-app” package in Ubuntu:
  Invalid

Bug description:
  mako build #183
  last known good  build: ?

  TEST CASE:
  1. Download 
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/AmosTV_10min_HT.divx
  2. Play it in the mediaplayer
  3. Once the video starts playing, if the control bar is not displayed tap the 
screen to display it
  4. Tap the slider to fast-forward to the middle of the video

  EXPECTED RESULT
  The video continues playing from the middle of the track

  ACTUAL RESULT
  The player hangs

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mediaplayer-app 0.20.5+14.10.20140718.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: armhf
  Date: Mon Aug 11 11:35:22 2014
  InstallationDate: Installed on 2014-08-11 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140811-020205)
  SourcePackage: mediaplayer-app
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1355095/+subscriptions

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

[Touch-packages] [Bug 1380736] Re: showing notification right after boot causes unity8 crash

[Olli Ries]

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

** Tags removed: rtm14

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

Title:
  showing notification right after boot causes unity8 crash

Status in Network Menu:
  Invalid
Status in “dbus-cpp” package in Ubuntu:
  Invalid
Status in “media-hub” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu RTM:
  Fix Released

Bug description:
  STEPS:
  1. Install a new image (Apparently it works with just re-running the wizard)
  2. While the dash is empty drag down the network indicator
  3. Click on the first unlock sim button
  4. Type in the unlock code and hit the tick
  5. System locks up

  EXPECTED:
  I expect the lock you unlock the sim and change back to the indicator

  ACTUAL:
  The system hard locks nothing works.  In the end you are forced to hard 
shutdown the phone by pressing and holding the power button till the phone 
powers down.

  Booting the Phone back up after this and everthing works as expected.
  Also waiting on the dash to fully load and fill with apps and then unlocking 
works.

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

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

[Touch-packages] [Bug 1385302] Re: Recorded videos don't show up in Videos scope

[Olli Ries]

** Tags added: ota-1

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

Title:
  Recorded videos don't show up in Videos scope

Status in Camera App:
  New
Status in libhybris:
  New
Status in “mediascanner2” package in Ubuntu:
  Invalid
Status in “qtubuntu-camera” package in Ubuntu:
  New
Status in “unity-scope-mediascanner” package in Ubuntu:
  Invalid

Bug description:
  File handles for recorded videos are left open until the camera app exits.
  This means they don't get detected by mediascanner (which waits for the file 
to finish being written) until you close the camera app, and presumably the 
operating system just closes all the handles.

  The impact is that your recorded videos won't show up anywhere that
  uses mediascanner (specifically the Videos scope).

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

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

[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Olli Ries]

** Summary changed:

- file corruption on touch images in rw portions of the filesystem
+ [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

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

Title:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

Status in “android” package in Ubuntu:
  Triaged
Status in “initramfs-tools-ubuntu-touch” package in Ubuntu:
  Triaged

Bug description:
  Symptoms are that cache files in /var/cache/apparmor and profiles in
  /var/lib/apparmor/profiles are sometimes corrupted after a reboot.
  We've already fixed several bugs in the apparmor and click-apparmor
  and made both more robust in the face of corruption and we've reduced
  the impact when there is a corrupted profile, but we've still not
  found the cause of the corruption. This corruption can still affect
  real-world devices: if a profile in /var/lib/apparmor/profiles is
  corrupted and the cache file is out of date, then the profile won't
  compile and that app/scope won't start.

  Workaround: remove the affected profile and then run 'sudo aa-
  clickhook'. This obviously is not viable on an end-user device.

  The investigation is ongoing and this may not be a problem with the
  kernel at all, so this bug may be retargeted to another project.

  The security team and the kernel team have discussed this a lot and
  Colin is currently looking at this. This bug is just so it can be
  tracked. Here is an excerpt from my latest email to Colin:

  "I believe I have conclusively ruled out apparmor_parser and aa-
  clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the
  test output:

  http://paste.ubuntu.com/8648109/

  Specifically, home/bug/test-with-true.sh changes the interesting parts
  of the algorithm to:

  1. wait for unity8 to start (this ensures the apparmor upstart job is 
finished)
  2. restore apparmor_parser and aa-clickhook, if needed
  3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles...
     /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser
     and aa-clickhook were /bin/true during boot so they could not have changed
     /var/lib/apparmor/profiles)
  4. verify the profiles, exit with error if they do not
  5. alternately upgrade/downgrade the packages
  6. verify the profiles, exit with error if they do not
  7. copy the known good profiles in the previous step to /home/bug/profiles...
  8. have apparmor_parser and aa-clickhook point to /bin/true
  9. reboot
  10. go to step 1

  In the paste you'll notice that in step 6 the profiles were
  successfully created by the installation of the packages, then
  verified, then copied aside, then apparmor_parser and aa-clickhook
  diverted, then rebooted, only to have the profiles in
  /var/lib/apparmor/profiles be different than what was copied aside. It
  would be nice to verify on your device as well (I reproduced several
  times here) and verify the reproducer algorithm. I think this suggests
  this is a kernel issue and not userspace.

  IMPORTANT: you will want to update the reproducer and refollow all of these 
steps (ie, I updated the scripts, the debs, the sudoers file, etc):
  $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz
  $ tar -zxvf ./aa-corruption.tar.gz
  ...

  $ adb push ./aa-corruption.tar.gz /tmp
  $ adb shell
  phablet@ubuntu-phablet:~$ cd /tmp
  phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz
  phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
  phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
  /etc/sudoers.d/
  phablet@ubuntu-phablet:~$ sudo mount -o remount,ro /
  phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home
  phablet@ubuntu-phablet:~$ exit
  $ cd ./aa-corruption
  $ ./test-from-host.sh
  ...

  The old script is still in place. Simply adjust ./test-from-host.sh to have:
  testscript=/home/bug/test.sh
  #testscript=/home/bug/test-with-true.sh"

  The kernel team has verified the above reproducer and symptoms.

  Related bugs:
  * bug 1371771
  * bug 1371765
  * bug 1377338

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

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

[Touch-packages] [Bug 1383357] Re: enabling flight mode shows airplane + [2g|3g] icon

[Olli Ries]

removed rtm tag in reference to comment #12, issue being tracked in
#1386109


** Tags removed: 2014-11-06 rtm14

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

Title:
  enabling flight mode shows airplane + [2g|3g] icon

Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “indicator-network” source package in Utopic:
  Invalid
Status in “network-manager” source package in Utopic:
  Confirmed
Status in “indicator-network” source package in Vivid:
  Invalid
Status in “network-manager” source package in Vivid:
  Triaged
Status in “indicator-network” package in Ubuntu RTM:
  Invalid

Bug description:
  
  known duplicate with different end result: bug #1386109

  

  NM fails to send a proper networking status updated signal.

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

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

[Touch-packages] [Bug 1387214] Re: file corruption on touch images in rw portions of the filesystem

[Olli Ries]

** Tags added: touch-2014-11-06

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

Title:
  file corruption on touch images in rw portions of the filesystem

Status in “android” package in Ubuntu:
  Triaged
Status in “initramfs-tools-ubuntu-touch” package in Ubuntu:
  Triaged
Status in “system-image” package in Ubuntu:
  Triaged

Bug description:
  Symptoms are that cache files in /var/cache/apparmor and profiles in
  /var/lib/apparmor/profiles are sometimes corrupted after a reboot.
  We've already fixed several bugs in the apparmor and click-apparmor
  and made both more robust in the face of corruption and we've reduced
  the impact when there is a corrupted profile, but we've still not
  found the cause of the corruption. This corruption can still affect
  real-world devices: if a profile in /var/lib/apparmor/profiles is
  corrupted and the cache file is out of date, then the profile won't
  compile and that app/scope won't start.

  Workaround: remove the affected profile and then run 'sudo aa-
  clickhook'. This obviously is not viable on an end-user device.

  The investigation is ongoing and this may not be a problem with the
  kernel at all, so this bug may be retargeted to another project.

  The security team and the kernel team have discussed this a lot and
  Colin is currently looking at this. This bug is just so it can be
  tracked. Here is an excerpt from my latest email to Colin:

  "I believe I have conclusively ruled out apparmor_parser and aa-
  clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the
  test output:

  http://paste.ubuntu.com/8648109/

  Specifically, home/bug/test-with-true.sh changes the interesting parts
  of the algorithm to:

  1. wait for unity8 to start (this ensures the apparmor upstart job is 
finished)
  2. restore apparmor_parser and aa-clickhook, if needed
  3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles...
     /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser
     and aa-clickhook were /bin/true during boot so they could not have changed
     /var/lib/apparmor/profiles)
  4. verify the profiles, exit with error if they do not
  5. alternately upgrade/downgrade the packages
  6. verify the profiles, exit with error if they do not
  7. copy the known good profiles in the previous step to /home/bug/profiles...
  8. have apparmor_parser and aa-clickhook point to /bin/true
  9. reboot
  10. go to step 1

  In the paste you'll notice that in step 6 the profiles were
  successfully created by the installation of the packages, then
  verified, then copied aside, then apparmor_parser and aa-clickhook
  diverted, then rebooted, only to have the profiles in
  /var/lib/apparmor/profiles be different than what was copied aside. It
  would be nice to verify on your device as well (I reproduced several
  times here) and verify the reproducer algorithm. I think this suggests
  this is a kernel issue and not userspace.

  IMPORTANT: you will want to update the reproducer and refollow all of these 
steps (ie, I updated the scripts, the debs, the sudoers file, etc):
  $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz
  $ tar -zxvf ./aa-corruption.tar.gz
  ...

  $ adb push ./aa-corruption.tar.gz /tmp
  $ adb shell
  phablet@ubuntu-phablet:~$ cd /tmp
  phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz
  phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
  phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
  /etc/sudoers.d/
  phablet@ubuntu-phablet:~$ sudo mount -o remount,ro /
  phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home
  phablet@ubuntu-phablet:~$ exit
  $ cd ./aa-corruption
  $ ./test-from-host.sh
  ...

  The old script is still in place. Simply adjust ./test-from-host.sh to have:
  testscript=/home/bug/test.sh
  #testscript=/home/bug/test-with-true.sh"

  The kernel team has verified the above reproducer and symptoms.

  Related bugs:
  * bug 1371771
  * bug 1371765
  * bug 1377338

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

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

[Touch-packages] [Bug 1336715] Re: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings

[Olli Ries]

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: High => Critical

** Changed in: unity8 (Ubuntu)
   Importance: High => Critical

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

Title:
  [TOPBLOCKER] switch-items in indicators sometimes get out of sync with
  system-settings

Status in Display Indicator:
  Invalid
Status in Indicator Location:
  Invalid
Status in Network Menu:
  Invalid
Status in Sound Menu:
  Invalid
Status in Ubuntu UX bugs:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  I noticed when testing flightmode with indicator-network that the
  switch items sometimes get out of sync from what GActions states on
  dbus are and stop updating their states when action states on dbus
  change.

  This seems to happen randomly and I have no procedure to reproduce
  reliably.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions

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

[Touch-packages] [Bug 1378043] Re: [TOPBLOCKER] Phone is getting locked during a call

[Olli Ries]

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

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

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

Title:
  [TOPBLOCKER] Phone is getting locked during a call

Status in Dialer app for Ubuntu Touch:
  Invalid
Status in Ubuntu UX bugs:
  Fix Committed
Status in “powerd” package in Ubuntu:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  The phone is getting lock during a call.

  How to reproduce
  

  1 - Open dialer app
  2 - Type a number
  3 - Click to call
  4 - Cover the proximity sensor
  5 - Uncover the proximity sensor

  Expected
  

  The phone shows the active call information

  Current results
  ===

  The phone get locked and you need to type your password to unlock it

  
  OBS:

  If you wait the call complete for about 3~ secs everything works nice.

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

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

[Touch-packages] [Bug 1381930] Re: [TOPBLOCKER] 7digital previews do not play in the scope

[Olli Ries]

set active tasks to critical to express that it's a [TOPBLOCKER]


** Changed in: qtubuntu-media (Ubuntu)
   Importance: Undecided => Critical

** Changed in: qtubuntu-media (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: unity-scopes-api (Ubuntu)
   Importance: Undecided => Critical

** Changed in: unity-scopes-api (Ubuntu RTM)
   Importance: Undecided => Critical

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

Title:
  [TOPBLOCKER] 7digital previews do not play in the scope

Status in “qtbase-opensource-src” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu:
  In Progress
Status in “unity-scope-mediascanner” package in Ubuntu:
  Invalid
Status in “unity-scopes-api” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu RTM:
  In Progress
Status in “unity-scopes-api” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  Invalid

Bug description:
  Steps to reproduce:

  1. Navigate to the music scope
  2. In the section 'New albums from 7digital' click on any album
  3. Press the play button on one of the track previews

  Expected result:

  The preview plays

  Actual result:

  No preview plays

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: armhf
  Date: Thu Oct 16 08:11:12 2014
  InstallationDate: Installed on 2014-10-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141016-010328)
  SourcePackage: unity-scope-mediascanner
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1376240] Re: pressing power button should silence incoming call

[Olli Ries]

** Changed in: unity-system-compositor
   Importance: Critical => High

** Changed in: telephony-service
   Importance: Critical => High

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

Title:
  pressing power button should silence incoming call

Status in Telephony Service:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in Unity System Compositor:
  In Progress
Status in “telephony-service” package in Ubuntu:
  New
Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  In the incoming call dialog there is no way to dismiss a call, only
  reject it.

  I would like a way to keep the calling active but in silent mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1376240/+subscriptions

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

[Touch-packages] [Bug 1355095] Re: mediaplayer hangs on fast-forward

[Olli Ries]

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

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

Title:
  mediaplayer hangs on fast-forward

Status in Media Hub:
  In Progress
Status in Media Player App:
  New
Status in “mediaplayer-app” package in Ubuntu:
  Invalid

Bug description:
  mako build #183
  last known good  build: ?

  TEST CASE:
  1. Download 
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/AmosTV_10min_HT.divx
  2. Play it in the mediaplayer
  3. Once the video starts playing, if the control bar is not displayed tap the 
screen to display it
  4. Tap the slider to fast-forward to the middle of the video

  EXPECTED RESULT
  The video continues playing from the middle of the track

  ACTUAL RESULT
  The player hangs

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mediaplayer-app 0.20.5+14.10.20140718.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: armhf
  Date: Mon Aug 11 11:35:22 2014
  InstallationDate: Installed on 2014-08-11 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140811-020205)
  SourcePackage: mediaplayer-app
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1355095/+subscriptions

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

[Touch-packages] [Bug 1350891] Re: [Dash] [design] Suru Background should scroll

[Olli Ries]

can't reproduce in #140/krillin

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

Title:
  [Dash] [design] Suru Background should scroll

Status in Clock application for Ubuntu devices:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  New

Bug description:
  On the dash, the Suru paper folds stays fixed at the bottom, while it
  should rather scroll away.

  We should also 'tile' the background, so the paper fold is displayed
  again after scrolling a certain amount of vertical space.

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

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

[Touch-packages] [Bug 1389165] Re: Some strings are not translatable

[Olli Ries]

** Tags added: rtm14 touch-2014-11-06

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

Title:
  Some strings are not translatable

Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  There are strings in the shell that are still not translatable
  ("Return to call"), and there's risk of more, since we were not
  extracting calls specifying the domain explicitly.

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

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

[Touch-packages] [Bug 1387261] Re: launcher badge missing due to dbus msgs getting lost

[Olli Ries]

** Tags added: touch-2014-11-06

** Tags added: rtm14

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

Title:
  launcher badge missing due to dbus msgs getting lost

Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  when there are image updates available, the system settings app in the 
launcher should have a small "badge" to reflect there's something new for the 
user, however this is missing.
  there's been a bit of debug done and it seems the message the launcher needs 
to act on goes missing on it's way from the backend via dbus.

  from design wrt missing image update badge on system settings
  " What you should see: "Wherever the System Settings icon appears, it should 
have a badge with the number of updates available." 
 "

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

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

[Touch-packages] [Bug 1378821] Re: today/yesterday label on sms and calls is incorrect

[Olli Ries]

not relevant to the target countries for RTM, pls fix in OTA

** Tags added: ota-1

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

Title:
  today/yesterday label on sms and calls is incorrect

Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  rtm image on krillin, build 88

  I'm in timzone UTC -4
  If I have a missed call or sms that shows up in the indicator, it will 
sometimes incorrect be displayed as "Yesterday"  even though it happened 
today. This happens if the missed call is anytime after 8pm local time.

  I believe it's because the determination for that label is using UTC
  time rather than converting to the local timezone. It should be
  changed to use local time zone.

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

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