[Touch-packages] [Bug 1665602] Re: nautilus no thumbnails for .jpg and .png

[Nick Dedekind]

This is still not working for me with SVGs.

libgdk-pixbuf2.0-0: 



  Installed: 2.36.5-3   



  Candidate: 2.36.5-3   



  Version table:



 *** 2.36.5-3 500   



500 http://gb.archive.ubuntu.com/ubuntu zesty/main amd64 Packages   



100 /var/lib/dpkg/status

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

Title:
  nautilus no thumbnails for .jpg and .png

Status in gnome-desktop:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  thumbnail for .tif is ok
  corrado@corrado-z2:~$ inxi
  CPU~Dual core Intel Core i3-4130 (-HT-MCP-) speed/max~3366/3400 MHz 
Kernel~4.10.0-8-generic x86_64 Up~1:03 Mem~983.2/7861.2MB HDD~1000.2GB(16.0% 
used) Procs~231 Client~Shell inxi~2.3.8  
  corrado@corrado-z2:~$ uname -a
  Linux corrado-z2 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-z2:~$ 
  display was ok with kernel 4.9.0-15
  corrado@corrado-z2:~$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.20.3-1ubuntu4
Candidate: 1:3.20.3-1ubuntu4
Version table:
   *** 1:3.20.3-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-z2:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.3-1ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Feb 17 11:22:50 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'search-view' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1329x774+49+24'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'larger'"
  InstallationDate: Installed on 2017-01-23 (24 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170123)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Touch-packages] [Bug 1674262] [NEW] Windows are not sized correctly if an invalid size comes from the state storage.

[Nick Dedekind]

Public bug reported:

The width/height of a windowed surface can be 0 if the initial size is
loaded with 0 due to an invalid state storage size.

http://paste.ubuntu.com/24195871/

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

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

Title:
  Windows are not sized correctly if an invalid size comes from the
  state storage.

Status in unity8 package in Ubuntu:
  New

Bug description:
  The width/height of a windowed surface can be 0 if the initial size is
  loaded with 0 due to an invalid state storage size.

  http://paste.ubuntu.com/24195871/

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

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

[Touch-packages] [Bug 1674263] [NEW] Window state storage should be using gu values rather than px

[Nick Dedekind]

Public bug reported:

Store the size (and position?) in GU values rather than px.

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

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

Title:
  Window state storage should be using gu values rather than px

Status in unity8 package in Ubuntu:
  New

Bug description:
  Store the size (and position?) in GU values rather than px.

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

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

[Touch-packages] [Bug 1664580] Re: Menus don't inform the app that the menu item is being hovered

[Nick Dedekind]

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  Menus don't inform the app that the menu item is being hovered

Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Our menu implementation doesn't trigger the QMenu::hovered signal

  This is typically used by apps to update the statusbar text that
  explains what the menu option does in more detail

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

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

[Touch-packages] [Bug 1664578] Re: Menus that fill themselves on QMenu::aboutToShow don't work

[Nick Dedekind]

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  Menus that fill themselves on QMenu::aboutToShow don't work

Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Our menu implementation doesn't trigger QMenu::aboutToShow so some
  menus in konsole and kate show up empty.

  QMenu::aboutToHide isn't sent either

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

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

[Touch-packages] [Bug 1663192] [NEW] Slider doesn't respect stepSize property

[Nick Dedekind]

Public bug reported:

Setting the stepSize property on the slider doesn't seem to have any
effect when dragging the slider tab with a mouse. If you set a range
between 0 and 10 with a step of 1, you will still get floating values
between the steps.

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

** Description changed:

- Setting the stepSize property on the slider doesnt seem to have any
- effect. If you set a range between 0 and 10 with a step of 1, you will
- still get floating values between the steps.
+ Setting the stepSize property on the slider doesn't seem to have any
+ effect when dragging the slider tab with a mouse. If you set a range
+ between 0 and 10 with a step of 1, you will still get floating values
+ between the steps.

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

Title:
  Slider doesn't respect stepSize property

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

Bug description:
  Setting the stepSize property on the slider doesn't seem to have any
  effect when dragging the slider tab with a mouse. If you set a range
  between 0 and 10 with a step of 1, you will still get floating values
  between the steps.

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

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

[Touch-packages] [Bug 1506753] Re: keyboard does pop up not after update to r26

[Nick Dedekind]

Ivo's bug logged https://bugs.launchpad.net/qtubuntu/+bug/1648842

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

Title:
  keyboard does pop up not after update to r26

Status in Canonical System Image:
  Incomplete
Status in ubuntu-keyboard package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu bq 4.5. Checked with browser, dekko, calendar and system
  settings (changing the pin). Turned the phone off and on.  No change.

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

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

[Touch-packages] [Bug 1647409] Re: Allow multiple trust prompts to be started per process

[Nick Dedekind]

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

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

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

Title:
  Allow multiple trust prompts to be started per process

Status in Mir:
  New
Status in QtMir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  The content-hub-service needs to be able to start prompt sessions for
  multiple requests.  Use cases:

  1. Paste Other from the UITK's TextField invokes the clipboard UI as a trust 
prompt started by content-hub-service
  2. Out of process peer picker, we have a new peer picker that doesn't run in 
the process of the requesting app.  It's started in a prompt session by 
content-hub-service
  3. Content picking.  The content-hub-service starts apps that provide a 
content picker in a trust prompt.

  All of these use cases require starting the prompt from the content-
  hub-service process.  We would like to do this without stopping other
  prompts that might already be in use.

  Currently we get the following exception:

  Invalid prompt session: Error processing request: Cannot start another prompt 
session
  Internal error details: 
/build/mir-S1BioZ/mir-0.24.1+16.04.20160928/src/server/frontend/session_mediator.cpp(1052):
 Throw in function virtual void 
mir::frontend::SessionMediator::start_prompt_session(const 
mir::protobuf::PromptSessionParameters*, mir::protobuf::Void*, 
google::protobuf::Closure*)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Cannot start another prompt session

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

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

[Touch-packages] [Bug 1646479] Re: Unity8 applications require access to name=com.ubuntu.MenuRegistrar

[Nick Dedekind]

** Description changed:

  All Qt applications running under unity8 require dbus access to
  name="com.ubuntu.MenuRegistrar"
  
  This will enable application menus for unity8 applications.
+ 
+ The interface is described here:
+ http://pastebin.ubuntu.com/23563719/
+ 
+ bus=session
+ path="/com/ubuntu/MenuRegistrar"
+ interface="com.ubuntu.MenuRegistrar"

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

Title:
  Unity8 applications require access to name=com.ubuntu.MenuRegistrar

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  All Qt applications running under unity8 require dbus access to
  name="com.ubuntu.MenuRegistrar"

  This will enable application menus for unity8 applications.

  The interface is described here:
  http://pastebin.ubuntu.com/23563719/

  bus=session
  path="/com/ubuntu/MenuRegistrar"
  interface="com.ubuntu.MenuRegistrar"

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

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

[Touch-packages] [Bug 1646479] [NEW] Unity8 applications require access to name=com.ubuntu.MenuRegistrar

[Nick Dedekind]

Public bug reported:

All Qt applications running under unity8 require dbus access to
name="com.ubuntu.MenuRegistrar"

This will enable application menus for unity8 applications.

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

** Summary changed:

- Apps using qtubuntu QPA require access to com.ubuntu.MenuRegistrar
+ Unity8 applications require access to com.ubuntu.MenuRegistrar

** Summary changed:

- Unity8 applications require access to com.ubuntu.MenuRegistrar
+ Unity8 applications require access to name=com.ubuntu.MenuRegistrar

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

Title:
  Unity8 applications require access to name=com.ubuntu.MenuRegistrar

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New

Bug description:
  All Qt applications running under unity8 require dbus access to
  name="com.ubuntu.MenuRegistrar"

  This will enable application menus for unity8 applications.

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

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

[Touch-packages] [Bug 1637155] Re: Only one tap to unmaximize window

[Nick Dedekind]

I think it might be recognising the single tap as a drag.

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

Title:
  Only one tap to unmaximize window

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

Bug description:
  bq M10 rc-proposed r219

  In desktop mode you need double tap to maximize an app window. But when the 
window is maximized to get it back to previous state it takes only one tap. I 
believe it should also be double tap.
  With only one tap you can't reveal window controls when it's maximized 
because after tapping it unaximize immediately.

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

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

[Touch-packages] [Bug 1627013] Re: Qt Drag and Drop across two windows of the same app is not detected

[Nick Dedekind]

We do not yet have support for drag and drop between windows.

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

Title:
  Qt Drag and Drop across two windows of the same app is not detected

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed

Bug description:
  What happened:
  1) Installed multi-window silo for the webbrowser [0] and installed demo app 
[1]
  2) Launched the multi window drag and drop example app, note sometimes the 
windows are spawned on top of each other, so you may need to move one to see 
both
  3) Attempt to drag one of the red boxes into the centre of the other window
  4) Notice that on unity7 the centre of the window turns green whereas on 
unity8 nothing happens
  5) Notice on unity7 that when the mouse is released the red box is moved into 
that window

  What I expected to happen:
  On unity8 for it to act the same as unity7, for the drag handle to work 
correctly and for the window droparea detection to work.

  Note at step 3 while dragging the box that on unity7 a handle
  correctly appears near the mouse and follows it, whereas on unity8 it
  spawns a window with the image for the handle but it doesn't follow
  the mouse. I am assuming this is linked to other existing bugs within
  unity8/mir where showing menus appear in separate windows? But I'm not
  sure which bug that is?

  I am currently assuming that either the increased security of Mir
  between windows is preventing the Qt drag system from being to detect
  when the mouse is over another window? (even though they are the same
  app)  Or is the issue that this functionality has not been implemented
  yet?

  I have the a xenial desktop with the stable overlay and the multi-
  window silo for the webbrowser [0]. The demo mini-app I have linked to
  this bug and can be found at [1]. Let me know if you need help running
  it.

  The use case for this scenario, is moving tabs in the webbrowser
  between multiple windows and dragging a tab out of a window to spawn a
  new window.

  0 - 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-084/+packages
  1 - https://code.launchpad.net/~ahayzen/+junk/multi-window-dnd-cpp-001

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

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

[Touch-packages] [Bug 1596524] Re: /usr/bin/webbrowser-app:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/qtubuntu/lp1596524.use-pbuffers

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

Title:
  /usr/bin/webbrowser-
  
app:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

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

  started with 0.23+15.04.20160615-0ubuntu1
  similar signature than bug 1596523

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

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

[Touch-packages] [Bug 1612346] Re: [MIR] qtubuntu

[Nick Dedekind]

** Description changed:

  [Availability]
   * Available in universe
  
  [Rationale]
   * This package is required by qt applications to run on mir.
  
  [Security]
   * Unknown
  
  [Quality assurance]
   * This package has no tests at this time.
  
  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
   * qtsensors-opensource-src (universe in xenial & yakkety)
   * platform-api (main in trusty only)
  
  [Standards compliance]
-  * This package uses cmake and is properly translated.
+  * This package uses qmake.
  
  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

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

Title:
  [MIR] qtubuntu

Status in qtubuntu package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by qt applications to run on mir.

  [Security]
   * Unknown

  [Quality assurance]
   * This package has no tests at this time.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
   * qtsensors-opensource-src (universe in xenial & yakkety)
   * platform-api (main in trusty only)

  [Standards compliance]
   * This package uses qmake.

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

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

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

[Touch-packages] [Bug 1612363] [NEW] [MIR] qmenumodel

[Nick Dedekind]

Public bug reported:

[Availability]
 * Available in universe

[Rationale]
 * This package is required by unity8

[Security]
 * Unknown

[Quality assurance]
 * This package has no tests.

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

[Standards compliance]
 * This package uses cmake.

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

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

** Description changed:

  [Availability]
-  * Available in universe
+  * Available in universe
  
  [Rationale]
-  * This package is required by unity8
+  * This package is required by unity8
  
  [Security]
-  * Unknown
+  * Unknown
  
  [Quality assurance]
-  * This package has no tests.
+  * This package has no tests.
  
  [Dependencies]
-  Most dependencies are already in main with the exception of the following:
-  * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
+  Most dependencies are already in main with the exception of the following:
+  * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
  
  [Standards compliance]
-  * This package uses cmake and is properly translated.
+  * This package uses cmake.
  
  [Maintenance]
-  * This package is maintained by Canonical and actively in use on the phone 
images
+  * This package is maintained by Canonical and actively in use on the phone 
images

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

Title:
  [MIR] qmenumodel

Status in qmenumodel package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * Unknown

  [Quality assurance]
   * This package has no tests.

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

  [Standards compliance]
   * This package uses cmake.

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

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

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

[Touch-packages] [Bug 1612358] [NEW] [MIR] qtmir

[Nick Dedekind]

Public bug reported:

[Availability]
 * Available in universe

[Rationale]
 * This package is required by unity8

[Security]
 * Unknown

[Quality assurance]
 * This package has unit tests.

[Dependencies]
 Most dependencies are already in main with the exception of the following:
 * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need a 
MIR?)
 * qtdeclarative-opensource-src-gles
 * lttng-ust
 * qtsensors-opensource-src

[Standards compliance]
 * This package uses cmake.

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

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

** Package changed: qtubuntu (Ubuntu) => qtmir (Ubuntu)

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

Title:
  [MIR] qtmir

Status in qtmir package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * Unknown

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
   * qtdeclarative-opensource-src-gles
   * lttng-ust
   * qtsensors-opensource-src

  [Standards compliance]
   * This package uses cmake.

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

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

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

[Touch-packages] [Bug 1612346] Re: [MIR] qtubuntu

[Nick Dedekind]

** Description changed:

  [Availability]
-  * Available in universe
+  * Available in universe
  
  [Rationale]
-  * This package is required by qt applications to run on mir.
+  * This package is required by qt applications to run on mir.
  
  [Security]
-  * Unknown
+  * Unknown
  
  [Quality assurance]
-  * This package has no tests at this time.
+  * This package has no tests at this time.
  
  [Dependencies]
-  Most dependencies are already in main with the exception of the following:
-  * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
-  * qtsensors-opensource-src (universe in xenial & yakkety)
-  * platform-api (main in trusty only)
+  Most dependencies are already in main with the exception of the following:
+  * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
+  * qtsensors-opensource-src (universe in xenial & yakkety)
+  * qtdeclarative-opensource-src-gles
+  * platform-api (main in trusty only)
  
  [Standards compliance]
-  * This package uses cmake and is properly translated.
+  * This package uses cmake and is properly translated.
  
  [Maintenance]
-  * This package is maintained by Canonical and actively in use on the phone 
images
+  * This package is maintained by Canonical and actively in use on the phone 
images

** Description changed:

  [Availability]
   * Available in universe
  
  [Rationale]
   * This package is required by qt applications to run on mir.
  
  [Security]
   * Unknown
  
  [Quality assurance]
   * This package has no tests at this time.
  
  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
   * qtsensors-opensource-src (universe in xenial & yakkety)
-  * qtdeclarative-opensource-src-gles
   * platform-api (main in trusty only)
  
  [Standards compliance]
   * This package uses cmake and is properly translated.
  
  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

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

Title:
  [MIR] qtubuntu

Status in qtubuntu package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by qt applications to run on mir.

  [Security]
   * Unknown

  [Quality assurance]
   * This package has no tests at this time.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
   * qtsensors-opensource-src (universe in xenial & yakkety)
   * platform-api (main in trusty only)

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

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

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

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

[Touch-packages] [Bug 1612346] [NEW] [MIR] qtubuntu

[Nick Dedekind]

Public bug reported:

[Availability]
 * Available in universe

[Rationale]
 * This package is required by qt applications to run on mir.

[Security]
 * Unknown

[Quality assurance]
 * This package has no tests at this time.

[Dependencies]
 Most dependencies are already in main with the exception of the following:
 * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need a 
MIR?)
 * qtsensors-opensource-src (universe in xenial & yakkety)
 * platform-api (main in trusty only)

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

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

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

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

Title:
  [MIR] qtubuntu

Status in qtubuntu package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by qt applications to run on mir.

  [Security]
   * Unknown

  [Quality assurance]
   * This package has no tests at this time.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
   * qtsensors-opensource-src (universe in xenial & yakkety)
   * platform-api (main in trusty only)

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

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

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

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

[Touch-packages] [Bug 1436405] Re: Duplicate menu (both unity and in-app) for Qt5 apps

[Nick Dedekind]

I've logged a bug with Qt.
https://bugreports.qt.io/browse/QTBUG-54793

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

Title:
  Duplicate menu (both unity and in-app) for Qt5 apps

Status in One Hundred Papercuts:
  Confirmed
Status in appmenu-qt5 package in Ubuntu:
  Confirmed
Status in libdbusmenu-qt package in Ubuntu:
  Confirmed

Bug description:
  At least konsole and khelpcenter suffers from this bug:

  Start the app inside the default Unity environment (not under KDE).
  Notice that the app's menubar appears twice.  Once in the upper row of
  the whole desktop, as expected and as it is for every Gnome app.  And
  also inside the application's window, wasting precious screen real
  estate.

  In Utopic, at least for konsole, I'm quite sure that the menu wasn't
  duplicated inside the app, it only appeared on the desktop's top Unity
  bar.

  (I'm not sure I guessed the component right; please reassign as
  appropriate.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 16:33:14 2015
  InstallationDate: Installed on 2012-05-30 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago)

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

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

[Touch-packages] [Bug 1436405] Re: Duplicate menu (both unity and in-app) for Qt5 apps

[Nick Dedekind]

I believe the issue may lie with Qt. QMenuBar only supports "native"
menu bars in OSX & windows CE as stated in
http://doc.qt.io/qt-5/qmenubar.html#nativeMenuBar-prop

This causes calls to QMenuBar::setVisible to fall through to
QWidget::setVisible which then sets the menu bar visual component of the
app window to visible.

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

Title:
  Duplicate menu (both unity and in-app) for Qt5 apps

Status in One Hundred Papercuts:
  Confirmed
Status in appmenu-qt5 package in Ubuntu:
  Confirmed
Status in libdbusmenu-qt package in Ubuntu:
  Confirmed

Bug description:
  At least konsole and khelpcenter suffers from this bug:

  Start the app inside the default Unity environment (not under KDE).
  Notice that the app's menubar appears twice.  Once in the upper row of
  the whole desktop, as expected and as it is for every Gnome app.  And
  also inside the application's window, wasting precious screen real
  estate.

  In Utopic, at least for konsole, I'm quite sure that the menu wasn't
  duplicated inside the app, it only appeared on the desktop's top Unity
  bar.

  (I'm not sure I guessed the component right; please reassign as
  appropriate.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 16:33:14 2015
  InstallationDate: Installed on 2012-05-30 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago)

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

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

[Touch-packages] [Bug 1596523] Re: /usr/bin/system-settings:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

[Nick Dedekind]

There doesn't seem to be a stack in that crash file and nothing evident
in the logs, so it be different; I'll keep trying to reproduce the
issue.

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

Title:
  /usr/bin/system-
  
settings:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding ubuntu-system-settings.  This problem was most recently seen
  with version 0.4+15.04.20160620.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/cd26f799c09a81efc74642f8628bbfe825caaf91
  contains more details.

  top 1 crash on rc-proposed
  started with 0.4+15.04.20160609-0ubuntu1

  signature similar to bug 1596524

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

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

[Touch-packages] [Bug 1596523] Re: /usr/bin/system-settings:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

[Nick Dedekind]

I'm after the console trace rather than the stacktrace; which should be
in the crash dump.

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

Title:
  /usr/bin/system-
  
settings:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding ubuntu-system-settings.  This problem was most recently seen
  with version 0.4+15.04.20160620.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/cd26f799c09a81efc74642f8628bbfe825caaf91
  contains more details.

  top 1 crash on rc-proposed
  started with 0.4+15.04.20160609-0ubuntu1

  signature similar to bug 1596524

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

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

[Touch-packages] [Bug 1596524] Re: /usr/bin/webbrowser-app:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

[Nick Dedekind]

If anyone can supply us with a crash dump, or an application log of this
happening, that would be very useful.

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

Title:
  /usr/bin/webbrowser-
  
app:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  New

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

  started with 0.23+15.04.20160615-0ubuntu1
  similar signature than bug 1596523

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

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

[Touch-packages] [Bug 1573153] Re: M10 tablet does not respect the orientation specified in .desktop file

[Nick Dedekind]

For now portrait apps will default to Side stage.

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

Title:
  M10 tablet does not respect the orientation specified in .desktop file

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

Bug description:
  Developers can restrict apps orientation by using
  X-Ubuntu-Supported-Orientations=portrait
  in .desktop file. Unfortunately it does not work in the new M10 tablet. You 
can see such app both in portrait and in landscape.

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

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

[Touch-packages] [Bug 1592404] Re: Moving scopes to side stage causes disapearance of stage and background

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/unity8/fix-dash-in-sidestage

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

Title:
  Moving scopes to side stage causes disapearance of stage and
  background

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

Bug description:
  1 - move scopes to side stage
  2. Switch between apps
  3. Restrt device

  What happens
  Side stage disapears, and starting up the primary stage is blank, dash home 
button does not reveal stage with scopes

  What should happen
  - stage is revealed consistent 
  - background shown with no other apps
  - side stage revealed at startup
  - side stage appears on hitting dash home if scopes wretched in the stage

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

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

[Touch-packages] [Bug 1566747] Re: Mir server with QtUbuntu client can cause system crash or Android GPU driver stall (Qualcomm)

[Nick Dedekind]

Confirmed fixed on n7 & n4. Marking as "Fix Released"

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

** Changed in: qtubuntu
   Status: Confirmed => Invalid

** Changed in: mir (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Mir server with QtUbuntu client can cause system crash or Android GPU
  driver stall (Qualcomm)

Status in Mir:
  Fix Released
Status in qtubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  While investigating new surface occlusion work in unity8 I've noticed that 
resizing a client multiple times can cause the system to either crash or a 
kworker process to cycle at 100% while attempting to reset the GPU.
  Only seems to occur on Qualcomm devices

  To Reproduce:
  I've written an extension for the demo server which can be found @ 
https://code.launchpad.net/~nick-dedekind/mir/occlusion-test-failures

  Server:
  mir_demo_server --test-resize [--test-resize-timeout=200]

  Client:
  QT_QPA_PLATFORM=ubuntumirclient qmlscene Test.qml

  -
  [Test.qml]
  Item {
     width: 700
     height: 1000
  }
  -

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

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

[Touch-packages] [Bug 1566747] Re: Mir server with QtUbuntu client can cause system crash or Android GPU driver stall (Qualcomm)

[Nick Dedekind]

I've done a quick test with 0.23 and it seems to work on my n7 now.
Will continue testing.

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

Title:
  Mir server with QtUbuntu client can cause system crash or Android GPU
  driver stall (Qualcomm)

Status in Mir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  While investigating new surface occlusion work in unity8 I've noticed that 
resizing a client multiple times can cause the system to either crash or a 
kworker process to cycle at 100% while attempting to reset the GPU.
  Only seems to occur on Qualcomm devices

  To Reproduce:
  I've written an extension for the demo server which can be found @ 
https://code.launchpad.net/~nick-dedekind/mir/occlusion-test-failures

  Server:
  mir_demo_server --test-resize [--test-resize-timeout=200]

  Client:
  QT_QPA_PLATFORM=ubuntumirclient qmlscene Test.qml

  -
  [Test.qml]
  Item {
     width: 700
     height: 1000
  }
  -

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

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

[Touch-packages] [Bug 1585910] Re: wantsDrag is always false in TouchGestureArea::resyncCachedTouchPoints

[Nick Dedekind]

I guess it should be the same as in updateTouchPoints.

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

Title:
  wantsDrag is always false in TouchGestureArea::resyncCachedTouchPoints

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Should we remove it?

  Or is there supposed some code that turns it to true that got lost
  somehow?

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

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

[Touch-packages] [Bug 1579003] Re: App stage not stored until app closed

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/unity8/sidestage-restoreOnRotation

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

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

Title:
  App stage not stored until app closed

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

Bug description:
  bq M10 rc-proposed OS build number r97

  Steps to reproduce:
  1. Close all apps
  2. In landscape open Settings app
  3. Move the app to side stage
  4. Rotate the tablet to portrait (Settings app takes all screen as expected)
  5. Rotate the tablet back to landscape

  Expected result:
  Settings app goes back to side stage

  What happens instead:
  Settings app is in main stage and side stage is empty

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

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

[Touch-packages] [Bug 1576239] Re: OSK not coming up after moving an app between stages

[Nick Dedekind]

** Branch linked: lp:~unity-team/unity8/sidestage-fixes

** Branch unlinked: lp:~nick-dedekind/unity8/sidestage-fixes

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

Title:
  OSK not coming up after moving an app between stages

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

Bug description:
  Steps to reproduce:

  * Have an app with TextField in the main stage
  * Trigger the OSK
  * 3-finger-drag the app into the side stage
  * focus the textfield again

  actual result:
  OSK not coming up

  expected result:
  OSK coming up

  Same happens the other way round, when dragging from side stage to
  main stage

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

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

[Touch-packages] [Bug 1576239] Re: OKS not coming up after moving an app between stages

[Nick Dedekind]

Caused by loss of active focus when creating the drag surface.

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

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

Title:
  OKS not coming up after moving an app between stages

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  * Have an app with TextField in the main stage
  * Trigger the OSK
  * 3-finger-drag the app into the side stage
  * focus the textfield again

  actual result:
  OSK not coming up

  expected result:
  OSK coming up

  Same happens the other way round, when dragging from side stage to
  main stage

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

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

[Touch-packages] [Bug 1573449] Re: osk doesn't work after putting app in or out sidestage

[Nick Dedekind]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  osk doesn't work after putting app in or out sidestage

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:
  Take an app and write something with the osk.
  Now put the app in the sidestage and try to type something with the osk. 
  The osk does not appear. 
  This happens more often, when the app was in the sidestage before and then 
dragged out in the "main view".

  Workaround:
  After putting an app in or out the sidestage, switch to the homescope and 
back to the app. The osk should appear again.

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

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

[Touch-packages] [Bug 1560188] Re: unity8 hang w/ CPU pegged

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/ubuntu-settings-components/calendar-
freeze

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

Title:
  unity8 hang w/ CPU pegged

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  To trigger:
  1. Wipe (or freshly flash) rc-proposed on a krillin or mako
  2. Log in, configure time zone
  3. Tilt the phone to make the screen rotate

  At this point, the UI stopped responding and 'top' showed 100% CPU
  being used by unity8.

  I tried to get data from gdb, but it wasn't very helpful:
  (gdb) bt
  #0  0xa803cce2 in ?? ()
  #1  0xa803cb98 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  More details are needed.

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

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

[Touch-packages] [Bug 1560039] Re: "Unlock SIM" untranslated in indicator network

[Nick Dedekind]

we need to migrate these translations from unity8 to ubuntu-settings-
components. The component was mistakenly added to the wrong project.

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

Title:
  "Unlock SIM" untranslated in indicator network

Status in Canonical System Image:
  New
Status in ubuntu-settings-components package in Ubuntu:
  New

Bug description:
  Test case.
  - Insert a SIM card.
  - Switch the phone to Spanish.
  - Reboot the phone.
  - Open indicator network.

  Expected result.
  - "Unlock SIM" button must appear in Spanish.

  Actual result.
  - "Unlock SIM" button displays the message in English.

  current build number: 286
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  The string appears in this file: /usr/lib/arm-linux-
  gnueabihf/qt5/qml/Ubuntu/Settings/Menus/ModemInfoItem.qml part of
  package qtdeclarative5-ubuntu-settings-components

  By the way, the string was also part of an old version of unity8.mo,
  but no longer ships it.

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

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

[Touch-packages] [Bug 1421696] Re: Ubuntu Phone notification: having to click on the icon is not obvious

[Nick Dedekind]

Is the UX spec given still current?

In the spec, all secondary actions have been removed from the
notification center (ie. no inline reply or callback for messages/missed
calls). This needs to be confirmed again by UX.

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

Title:
  Ubuntu Phone notification: having to click on the icon is not obvious

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-messages package in Ubuntu:
  Invalid
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In the BQ E4.5 Ubuntu Edition, if you got a new notification, you have
  to click just in the icon for going to the application.

  By example: You receive a Telegram message. You dragdown the status
  bar (green envelope) and you see the message. If you click in the
  notification nothing happens. You need to click in its icon.

  This is not intuitive.

  Thanks in advance!

  -- UX Comment --

  We've added in the latest specification for Notifications in the
  Notification Centre the ability to launch the originating app by
  tapping on any part of the body of a notification list item. Page 29:
  Link to the
  
spec:https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.2kihdtv7as7e

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

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

[Touch-packages] [Bug 1550327] Re: Invalid use of selected.backgroundText

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/ubuntu-settings-components
/indicator-color-fixes

** Changed in: ubuntu-settings-components (Ubuntu)
 Assignee: Andrea Cimitan (cimi) => Nick Dedekind (nick-dedekind)

** Changed in: unity8 (Ubuntu)
 Assignee: Andrea Cimitan (cimi) => Nick Dedekind (nick-dedekind)

** Branch linked: lp:~nick-dedekind/unity8/indicator-color-fixes

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

Title:
  Invalid use of selected.backgroundText

Status in Canonical System Image:
  Triaged
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  The selected.backgroundText color (what is sparkling blue) of the
  palette can be used only when it is appropriate. So for selected texts
  what are in background.

  For example in the http://bazaar.launchpad.net/~unity-
  team/unity8/trunk/view/head:/qml/Panel/Indicators/ModemInfoItem.qml

  Icon {
  id: statusIcon
  color: theme.palette.selected.backgroundText

  Layout.preferredHeight: parent.height
  Layout.preferredWidth: Layout.preferredHeight

  visible: name !== ""
  }

  What looks like this -> http://picpaste.com/pics/indicator-
  FMruC8JY.1456490460.png

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

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

[Touch-packages] [Bug 1548696] [NEW] App is continuously redrawing even though there is nothing changing visually

[Nick Dedekind]

Public bug reported:

Start app with QT_LOGGING_RULES="qt.scenegraph.renderloop=true"

You will continuously get:
qt.scenegraph.renderloop: polishAndSync (normal) QQuickView(0x204ca58)
amongst many others, which indicate that the UI is being redrawn.

Even with occlusion enabled, we still get:
qt.scenegraph.renderloop: - ticking non-visual timer

There may be a hidden activity indicator which is set to running even
though not visible.

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

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

Title:
  App is continuously redrawing even though there is nothing changing
  visually

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Start app with QT_LOGGING_RULES="qt.scenegraph.renderloop=true"

  You will continuously get:
  qt.scenegraph.renderloop: polishAndSync (normal) QQuickView(0x204ca58)
  amongst many others, which indicate that the UI is being redrawn.

  Even with occlusion enabled, we still get:
  qt.scenegraph.renderloop: - ticking non-visual timer

  There may be a hidden activity indicator which is set to running even
  though not visible.

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

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

[Touch-packages] [Bug 1543132] Re: unity::scopes::internal::OnlineAccountClientImpl::flush_pending_session gets stuck and freezes UI

[Nick Dedekind]

Yeah, this is definitely different.  After I have added a google
account, i don't get the login button. I haven't tried after rebooting
with a google account already set up.

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

Title:
  unity::scopes::internal::OnlineAccountClientImpl::flush_pending_session
  gets stuck and freezes UI

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Today's image

  I have a google account setup in system settings and i have enabled
  youtube in settings

  When i go to the youtube scope i still see the "Log-in to youtube"
  button (which idellay i should not see, but that's not the problem)

  When i click the button the ui freezes forever

  Backtrace is http://paste.ubuntu.com/14993287/

  My totally uninformed guess is that Thread 3 is stuck for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1543132/+subscriptions

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

[Touch-packages] [Bug 1534541] Re: Dash doesn't accept input (appears frozen) after youtube scope auth

[Nick Dedekind]

No events from the client input receiver. or the unity8 server input
log; so it seems it's a u8/qtmir issue.

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

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

Title:
  Dash doesn't accept input (appears frozen) after youtube scope auth

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  1. Make sure youtube scope is not favorited.
  2. Remove Google account from Accounts settings.
  3. Open youtube scope via Manage Dash
  4. Hit the orange 'Log-in to..' button
  5. Authenticate with google.
  6. Wait till youtube results are refreshed.

  The dash appears frozen now. It doesn't crash though, in fact the
  process is running and the dash responds to the dbus signal which
  invalidates current scope and forces a refresh (tested with dbus-send
  --session --type=signal '/com/canonical/unity/scopes'
  com.canonical.unity.scopes.InvalidateResults string:'clickscope').

  Note, the launcher as well as apps still receive input and work ok.

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

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

[Touch-packages] [Bug 1536662] Re: [regression] Mir hangs and then crashes due to reading from /dev/random

[Nick Dedekind]

qtmir server plugin will time out waiting for mir thread to start after
10 seconds; should we increase this to match?

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

Title:
  [regression] Mir hangs and then crashes due to reading from
  /dev/random

Status in Mir:
  In Progress
Status in Unity System Compositor:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  cookie_factory attempts to read data from /dev/random at boot, and
  blocks until it has enough random data or timesout after 30 seconds.

  How I can reproduce
  1. Run the Unity8 greeter as a mir server
  2. Reboot

  Expected behavior: Greeter is displayed as mir && USC run happily
  Actual behavior: Mir throws an exception after 30 seconds

  Work-around:
  Before logging in, move the mouse around lots, for at least 20 seconds. And 
after logging in, while you're looking at a black screen, move the mouse around 
furiously. This will populate the kernel entropy pool sufficiently to avoid the 
hang and crash.

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

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

[Touch-packages] [Bug 1475678] Re: Unity8 not informing clients that they are not visible and thus can stop rendering

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/qtubuntu/occlusion-2.0

** Branch linked: lp:~nick-dedekind/qtmir/occlusion-2.0

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

Title:
  Unity8 not informing clients that they are not visible and thus can
  stop rendering

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

Bug description:
  Currently on the phone, apps stop rendering when shell hides them,
  because shell also lifecycle stops the app. App isn't actually told it
  should stop rendering, we just SIGSTOP its process.

  But some apps are not lifecycle stopped, e.g. music. So we should have
  unity8 tell the app to stop rendering.

  
  This will be a multi-step process:
  1. Qtubuntu
  Mir has a attribute to set on surfaces to tell them they are 
visible/occluded: (see mir/include/common/mir_toolkit/common.h)
  mir_surface_attrib_visibility - part of the MirSurfaceAttrib enum. 

  This indicates these possible values:
  typedef enum MirSurfaceVisibility
  {
  mir_surface_visibility_occluded = 0,
  mir_surface_visibility_exposed
  } MirSurfaceVisibility;

  On the client side (qtubuntu), you need to listen for this attribute change, 
and connect it to QWindowSystemInterface::handleExposeEvent() which tells Qt 
how much of a QWindow is being drawn.
  Note there is also a QWindowSystemInterface::handleWindowStateChanged() 
handler, which use use to explicitly set QWindow show/hide, but Qt tends to 
release its GL context on hide, which we may not desire. It may not hurt, worth 
a look.

  2. QtMir
  There are methods on mir::scene::Surface to set and get the MirSurfaceAttrib 
attributes. I think it would make sense to use the pre-existing 
MirSurfaceItem::visible property, so that if a surface is marked visible=false, 
then that will dispatch the mir_surface_visibility_occluded event to the 
client, so it will stop drawing.

  3. Unity8
  Correctly set visible=false when an application surface is occluded, and true 
when visible. QML has no automatic way of doing that (i.e. occlusion detection)

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

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

[Touch-packages] [Bug 1520548] Re: Volume slider in sound indicator ignores the "volume" action coming from indicator-sound in a particular case

[Nick Dedekind]

** Branch linked: lp:~xavi-garcia-mena/indicator-sound/action-sync-
volume

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

Title:
  Volume slider in sound indicator ignores the "volume" action coming
  from indicator-sound in a particular case

Status in unity8 package in Ubuntu:
  New

Bug description:
  To re-create this:

  Use last rc flash image.

  1. Plug headphones in
  2. Play audio multimedia
  3. Open the sound indicator
  4. Move the volume slider to the maximum
  A warning dialog should appear asking the user to approve high volume
  At this point the indicator-sound has clamped the volume to 75% waiting 
for the user to accept or decline the warning.
  5. Press cancel
  6. The slider shows the value over 75%

  I can see with dbus-monitor that the volume action signal is emitted
  with the 75% value, although it seems that the UI is ignoring it.

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

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

[Touch-packages] [Bug 1520548] Re: Volume slider in sound indicator ignores the "volume" action coming from indicator-sound in a particular case

[Nick Dedekind]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  Volume slider in sound indicator ignores the "volume" action coming
  from indicator-sound in a particular case

Status in unity8 package in Ubuntu:
  New

Bug description:
  To re-create this:

  Use last rc flash image.

  1. Plug headphones in
  2. Play audio multimedia
  3. Open the sound indicator
  4. Move the volume slider to the maximum
  A warning dialog should appear asking the user to approve high volume
  At this point the indicator-sound has clamped the volume to 75% waiting 
for the user to accept or decline the warning.
  5. Press cancel
  6. The slider shows the value over 75%

  I can see with dbus-monitor that the volume action signal is emitted
  with the 75% value, although it seems that the UI is ignoring it.

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

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

[Touch-packages] [Bug 1520548] Re: Volume slider in sound indicator ignores the "volume" action coming from indicator-sound in a particular case

[Nick Dedekind]

The UI is stuck in a "waiting for server" state.  We are using a live
slider, and constantly sending updates to the server. And since the
server stops responding to our requests (doesn't set the value to above
75% until we let it) we stick in this state for a timeout (up to 30
seconds), after which we will reset to the server state.

So we do eventually end up in the correct value, but it takes time.

This is because if we responded directly to every server change, the UI
would be unusable (slider would bob/stutter about as we drag it). We
can't do much about the server silently rejecting change requests other
than re-syncing the server value after a time.


That being said, I've had a bit of a thought.
We basically need some feedback from the server to cause a "reset to server 
value". Could we add an action to the backend for this? Think of it like a 
"in-sync number". If we detect an increment to the sync number, we re-sync to 
the server value. The backend could increment the action value after the user 
decision on the snap decision.

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

Title:
  Volume slider in sound indicator ignores the "volume" action coming
  from indicator-sound in a particular case

Status in unity8 package in Ubuntu:
  New

Bug description:
  To re-create this:

  Use last rc flash image.

  1. Plug headphones in
  2. Play audio multimedia
  3. Open the sound indicator
  4. Move the volume slider to the maximum
  A warning dialog should appear asking the user to approve high volume
  At this point the indicator-sound has clamped the volume to 75% waiting 
for the user to accept or decline the warning.
  5. Press cancel
  6. The slider shows the value over 75%

  I can see with dbus-monitor that the volume action signal is emitted
  with the 75% value, although it seems that the UI is ignoring it.

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

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

[Touch-packages] [Bug 1514556] Re: With occlusion detection, apps stop responding when switching from another app.

[Nick Dedekind]

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

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

** No longer affects: unity8 (Ubuntu)

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

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

** Changed in: qtmir (Ubuntu)
   Importance: Undecided => Critical

** Changed in: qtubuntu (Ubuntu)
   Importance: Undecided => Critical

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  With occlusion detection, apps stop responding when switching from
  another app.

Status in Canonical System Image:
  In Progress
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  If you switch from one app to the next, and start scrolling around (eg
  in dash) very soon after switching, the app will sometimes stop
  rendering.

  Reproduce:
  1) Start an app (eg dialer) from dash
  2) wait a few seconds in dialer.
  3) Do a quick switch back to dash, and immediately start scrolling/swiping 
around.

  Expected:
  app behaves normally and responds to user input.

  Actual:
  sometimes the dash will stop responding for an undetermined amount of time, 
or until you interact with another part of the shell.

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

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

[Touch-packages] [Bug 1514556] Re: With occlusion detection, apps stop responding when switching from another app.

[Nick Dedekind]

Testing in Ubuntu 15.04 (r168):

This problem seems to be related to mir dropping old buffers when the 
visibility changes from occluded->exposed.
If I remove the "drop old buffers" code from 
mir::scene::BasicSurface::set_visibility, then it seems to come right.

There have been some changes in mir related to the buffer stream and
arbiter which I'm testing if might make a difference. It may also be
that we're not handling the dropped buffers correctly in qtmir?

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

Title:
  With occlusion detection, apps stop responding when switching from
  another app.

Status in Canonical System Image:
  In Progress
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  If you switch from one app to the next, and start scrolling around (eg
  in dash) very soon after switching, the app will sometimes stop
  rendering.

  Reproduce:
  1) Start an app (eg dialer) from dash
  2) wait a few seconds in dialer.
  3) Do a quick switch back to dash, and immediately start scrolling/swiping 
around.

  Expected:
  app behaves normally and responds to user input.

  Actual:
  sometimes the dash will stop responding for an undetermined amount of time, 
or until you interact with another part of the shell.

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

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

[Touch-packages] [Bug 1514556] [NEW] With occlusion detection, apps stop responding when switching from another app.

[Nick Dedekind]

Public bug reported:

If you switch from one app to the next, and start scrolling around (eg
in dash) very soon after switching, the app will sometimes stop
rendering.

Reproduce:
1) Start an app (eg dialer) from dash
2) wait a few seconds in dialer.
3) Do a quick switch back to dash, and immediately start scrolling/swiping 
around.

Expected:
app behaves normally and responds to user input.

Actual:
sometimes the dash will stop responding for an undetermined amount of time, or 
until you interact with another part of the shell.

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

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

Title:
  With occlusion detection, apps stop responding when switching from
  another app.

Status in unity8 package in Ubuntu:
  New

Bug description:
  If you switch from one app to the next, and start scrolling around (eg
  in dash) very soon after switching, the app will sometimes stop
  rendering.

  Reproduce:
  1) Start an app (eg dialer) from dash
  2) wait a few seconds in dialer.
  3) Do a quick switch back to dash, and immediately start scrolling/swiping 
around.

  Expected:
  app behaves normally and responds to user input.

  Actual:
  sometimes the dash will stop responding for an undetermined amount of time, 
or until you interact with another part of the shell.

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

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

[Touch-packages] [Bug 1512794] Re: With occlusion detection, apps under greeter still render

[Nick Dedekind]

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

** No longer affects: unity8

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

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

** Changed in: qtmir (Ubuntu)
   Importance: Undecided => High

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

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

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

Title:
  With occlusion detection, apps under greeter still render

Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps:
  * get http://pastebin.ubuntu.com/12998333/
  * lock your phone
  * turn the screen on
  * run with:
$ QSG_RENDERER_DEBUG=render qmlscene tmp.qml --desktop_file_hint=unity8
  * use the launcher to focus a different app

  Expected:
  * no render prints until you unlock and focus the app

  Current:
  * rendering all the time

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20151102-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-021]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Nov  3 16:41:03 2015
  InstallationDate: Installed on 2015-11-03 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20151103-020303)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1351109] Re: No way to clean up a UASensorsHaptic when finished with it

[Nick Dedekind]

This is causing qt apps to crash when they exit cleanly (eg qml:
Qt.quit()) .

** Changed in: platform-api (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  No way to clean up a UASensorsHaptic when finished with it

Status in platform-api:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress

Bug description:
  There's a ua_sensors_haptic_new() function to create a UASensorsHaptic
  object, but no way to close its resources when done, e.g. an  unref or
  delete func.

  Use case: automated tests for client code that uses
  ua_sensors_haptic_*() and needs to be able to repeatedly start a new
  bus and then tear it down cleanly when the test is done.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Nick Dedekind]

** Branch linked: lp:~aacid/ubuntu-ui-toolkit/LiveTimer

** Branch linked: lp:~aacid/ubuntu-ui-toolkit/i18n-RelativeDateTime

** Branch unlinked: lp:~nick-dedekind/ubuntu-ui-toolkit/lp1378821.time-
translation

** Branch unlinked: lp:~nick-dedekind/ubuntu-ui-toolkit/LiveTimer

** Branch unlinked: lp:~nick-dedekind/ubuntu-ui-toolkit/i18n-
RelativeDateTime

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

Title:
  SMS notification: time format not translatable

Status in Canonical System Image:
  In Progress
Status in Ubuntu Translations:
  Triaged
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

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 1493530] Re: /usr/bin/unity8-dash:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString

[Nick Dedekind]

Don't think we can trust this stacktrace. Seems impossible to get there.

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

Title:
  
/usr/bin/unity8-dash:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20150821-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/4b65a8a3a3b3a1ec81d12698b84dc4e8dda85187
  contains more details.

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

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

[Touch-packages] [Bug 1493530] Re: /usr/bin/unity8-dash:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString

[Nick Dedekind]

Have we got an crash dump files?

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

Title:
  
/usr/bin/unity8-dash:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20150821-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/4b65a8a3a3b3a1ec81d12698b84dc4e8dda85187
  contains more details.

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

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

[Touch-packages] [Bug 1489076] Re: clicking on active call banner and indicators with mouse

[Nick Dedekind]

There are a couple of MouseAreas stealing the presses, but we do need a
UX decision about what happens when you click on the indicators during
an active call. I think the indicators should show, otherwise there is
no other way to open them during a call.

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

Title:
  clicking on active call banner and indicators with mouse

Status in canonical-pocket-desktop:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  possibly related to bug 1473571 &  bug 1473566

  on windowed mode vivid+o + silo0
  when in an active call, set dialer app to the background to activate the 
green banner (active call banner)
  using BT connected mouse click on the banner or the indicators and nothing 
happens

  there is also a design question of what is to happen in this case with
  the indicators? should a click reveal ? or should indicators be kept
  to a non-green area when a monitor is connected? could get tricky
  quick

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1489076/+subscriptions

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

[Touch-packages] [Bug 1434584] Re: closing an app by swiping it should graceful quit

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/qtmir/polite-close

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

Title:
  closing an app by swiping it should graceful quit

Status in QtMir:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  By swiping an app to close causes the app to quit without call its
  destructor. In my opinion we should use the same behavior as we have
  on desktop when clicking on the "x" in the windows manager.

  Most of c++ classes has some cleanup function on the destructor and it
  expected that will be called at some point. For example the
  QTemporaryFile or QTemporaryDir. They remove the files created during
  the destruction.

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

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

[Touch-packages] [Bug 1358340] Re: [Indicators] Complete greeter profiles

[Nick Dedekind]

I don't think we need to worry about this re profiles. The
implementation of what the options in Settings do is a design/backend
decision. I believe the defaults are correct already.

That said, we should enable the indicator profile switching.

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Nick Dedekind (nick-dedekind)

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

Title:
  [Indicators] Complete greeter profiles

Status in Indicator Date and Time:
  Invalid
Status in Messaging Menu:
  Fix Released
Status in Transfer Indicator:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in Unity 8:
  Fix Released
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking

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

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

[Touch-packages] [Bug 1453217] Re: [indicators] tap to return to call shouldn't expand indicators

[Nick Dedekind]

** Changed in: unity8 (Ubuntu)
   Importance: Low = High

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

Title:
  [indicators] tap to return to call shouldn't expand indicators

Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Vivid r 207

  steps to reproduce:

  1. call device
  2. accept call
  3. navigate away, e.g. dash, different app...
  4. the indicator panel should be now green and say tap to return to call
  5. tap the panel

  actual result:
  The panel expands 1/3 of the screen and then navigates back to the active 
call screen.

  ---UX comment/expected result-

  The panel should not expand at all during the duration of the call and
  just navigate back to the calling screen.

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

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

[Touch-packages] [Bug 1450229] Re: avatar in notification has wrong aspect ratio

[Nick Dedekind]

** Changed in: ubuntu-settings-components (Ubuntu)
 Assignee: (unassigned) = Nick Dedekind (nick-dedekind)

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: Confirmed = In Progress

** Branch linked: lp:~nick-dedekind/ubuntu-settings-components/icon-
aspect-ratio-crop

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

Title:
  avatar in notification has wrong aspect ratio

Status in Canonical System Image:
  New
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  the avatar thumbnail is wrong in the notifciation bubble and doesn't
  have correct aspect ration.

  Steps to reproduce

  1) take a picture on the phone and associate with a contact that will text 
the phone
  2) text the phone from the contact that has the avatar

  Expected results:
  notification bubble will show properly scaled avatar

  Actual results:
  avatar is not scaled correctly

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/unity8/lp1378821.time-translation

-- 
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 Canonical System Image:
  In Progress
Status in Ubuntu Translations:
  Triaged
Status in telephony-service package in Ubuntu:
  Invalid
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu RTM:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  New
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 1468042] Re: Notifications of incoming messages are displayed on the lockscreen even though they are disabled.

[Nick Dedekind]

We should be using thje greeter profile which shouln't include various
things based on the indicator security settings. If we're changing the
profile correctly, then it's up to indicator-messaging to obey.

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

Title:
  Notifications of incoming messages are displayed on the lockscreen
  even though they are disabled.

Status in unity8 package in Ubuntu:
  New

Bug description:
  I have disabled Notifications and quick settings in System Settings,
  yet notifications of incoming messages are still displayed on the
  lockscreen, including the first line or so of the message.

  I'm on a bq Aquaris 4.5 with r23 installed (and all updates applied as
  of writing this).

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

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

[Touch-packages] [Bug 1468308] [NEW] TextArea is showing scrollbars when initially empty and using autoSize

[Nick Dedekind]

Public bug reported:

If the TextArea is using autoSize=true and has no text in it, the
vertical scrollbar shows on start. If you edit to multiple lines, then
remove the text, the scrollbar no longer shows.

Test Case:

import QtQuick 2.3
import Ubuntu.Components 1.2

Item {
width: units.gu(20)
height: units.gu(20)
TextArea {
autoSize: true
anchors {
left: parent.left
right: parent.right
}
}
}

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

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

Title:
  TextArea is showing scrollbars when initially empty and using autoSize

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

Bug description:
  If the TextArea is using autoSize=true and has no text in it, the
  vertical scrollbar shows on start. If you edit to multiple lines, then
  remove the text, the scrollbar no longer shows.

  Test Case:

  import QtQuick 2.3
  import Ubuntu.Components 1.2

  Item {
  width: units.gu(20)
  height: units.gu(20)
  TextArea {
  autoSize: true
  anchors {
  left: parent.left
  right: parent.right
  }
  }
  }

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

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

[Touch-packages] [Bug 1453217] Re: [indicators] tap to return to call shouldn't expand indicators

[Nick Dedekind]

@kevin - sure. It gets a bit wacky in the panel code, but they'll be
fine.

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

Title:
  [indicators] tap to return to call shouldn't expand indicators

Status in Ubuntu UX bugs:
  Triaged
Status in dialer-app package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Vivid r 207

  steps to reproduce:

  1. call device
  2. accept call
  3. navigate away, e.g. dash, different app...
  4. the indicator panel should be now green and say tap to return to call
  5. tap the panel

  actual result:
  The panel expands 1/3 of the screen and then navigates back to the active 
call screen.

  ---UX comment/expected result-

  The panel should not expand at all during the duration of the call and
  just navigate back to the calling screen.

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

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

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

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/ubuntu-settings-components/fix-
maximumWaitBufferInterval

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

Title:
  Three consistent autopilot test failures

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

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

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

  Example run:

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

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

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

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

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

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

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

[Touch-packages] [Bug 1453836] Re: When changing a slider value inside a nested Flickable, the bottom flickable can steal the mouse events.

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/ubuntu-ui-toolkit/prevent-slider-
mouse-stealing

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

Title:
  When changing a slider value inside a nested Flickable, the bottom
  flickable can steal the mouse events.

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

Bug description:
  The slider position change event is not preventing the event from being 
stolen by a parent if the Flickable is inside another Flickable (somewhere in 
the tree). It's only looking at the first parent Flickable.
  QtQuick.Controls.Slider works around this by using the preventStealing 
property.

  Test Script:

  import QtQuick 2.0
  import Ubuntu.Components 1.1

  Item {
  height: units.gu(50)
  width: units.gu(50)

  Flickable {
  anchors.fill: parent
  contentWidth: flickInner.width

  Flickable {
  id: flickInner
  width: units.gu(100)
  anchors.top: parent.top
  anchors.bottom: parent.bottom
  contentHeight: inner.height

  Item {
  id: inner
  height: units.gu(100)
  Slider {}
  }
  }
  }
  }

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

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

[Touch-packages] [Bug 1453836] [NEW] When changing a slider value inside a nested Flickable, the bottom flickable can steal the mouse events.

[Nick Dedekind]

Public bug reported:

The slider position change event is not preventing the event from being stolen 
by a parent if the Flickable is inside another Flickable (somewhere in the 
tree). It's only looking at the first parent Flickable.
QtQuick.Controls.Slider works around this by using the preventStealing property.

Test Script:

import QtQuick 2.0
import Ubuntu.Components 1.1

Item {
height: units.gu(50)
width: units.gu(50)

Flickable {
anchors.fill: parent
contentWidth: flickInner.width

Flickable {
id: flickInner
width: units.gu(100)
anchors.top: parent.top
anchors.bottom: parent.bottom
contentHeight: inner.height

Item {
id: inner
height: units.gu(100)
Slider {}
}
}
}
}

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

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

Title:
  When changing a slider value inside a nested Flickable, the bottom
  flickable can steal the mouse events.

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

Bug description:
  The slider position change event is not preventing the event from being 
stolen by a parent if the Flickable is inside another Flickable (somewhere in 
the tree). It's only looking at the first parent Flickable.
  QtQuick.Controls.Slider works around this by using the preventStealing 
property.

  Test Script:

  import QtQuick 2.0
  import Ubuntu.Components 1.1

  Item {
  height: units.gu(50)
  width: units.gu(50)

  Flickable {
  anchors.fill: parent
  contentWidth: flickInner.width

  Flickable {
  id: flickInner
  width: units.gu(100)
  anchors.top: parent.top
  anchors.bottom: parent.bottom
  contentHeight: inner.height

  Item {
  id: inner
  height: units.gu(100)
  Slider {}
  }
  }
  }
  }

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Nick Dedekind]

I used a component because using function won't respond to changes in locale, 
time-zone, daylight savings, etc without a refresh of the data.
It's a lot more complicated than just a i18n.tr(12:00 PM) kind of thing. 
Unless you have a better idea (other than ignoring changes).

-- 
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:
  In Progress
Status in Ubuntu Translations:
  Triaged
Status in telephony-service package in Ubuntu:
  Invalid
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu RTM:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  New
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 1396058] Re: [Messaging Menu] Using enter in the messaging menu entry looks like it sends the reply when it doesn't

[Nick Dedekind]

** Changed in: indicator-messages (Ubuntu)
   Status: New = Invalid

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: New = Confirmed

** Changed in: messaging-app
   Status: New = Invalid

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

Title:
  [Messaging Menu] Using enter in the messaging menu entry looks like
  it sends the reply when it doesn't

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Messaging App:
  Invalid
Status in Ubuntu UX bugs:
  Won't Fix
Status in indicator-messages package in Ubuntu:
  Invalid
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed

Bug description:
  Using rtm 169
  - receive a sms
  - read it in the messaging menu and decide to reply inline
  - enter something and hit return/enter on the osk

  - the text entry is dismissed and the osk hidden, it looks like the
  message was sent, where in fact it was not

  UX comment-

  We've added in the latest specification for the notification system
  the behaviour of the notification items in the messaging
  menu/notification centre. Link to the spec:
  
https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.aarksr1t9zhb

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

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

[Touch-packages] [Bug 1396058] Re: [Messaging Menu] Using enter in the messaging menu entry looks like it sends the reply when it doesn't

[Nick Dedekind]

** Changed in: ubuntu-settings-components (Ubuntu)
 Assignee: (unassigned) = Nick Dedekind (nick-dedekind)

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

Title:
  [Messaging Menu] Using enter in the messaging menu entry looks like
  it sends the reply when it doesn't

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Messaging App:
  Invalid
Status in Ubuntu UX bugs:
  Won't Fix
Status in indicator-messages package in Ubuntu:
  Invalid
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed

Bug description:
  Using rtm 169
  - receive a sms
  - read it in the messaging menu and decide to reply inline
  - enter something and hit return/enter on the osk

  - the text entry is dismissed and the osk hidden, it looks like the
  message was sent, where in fact it was not

  UX comment-

  We've added in the latest specification for the notification system
  the behaviour of the notification items in the messaging
  menu/notification centre. Link to the spec:
  
https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.aarksr1t9zhb

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

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

[Touch-packages] [Bug 1396058] Re: [Messaging Menu] Using enter in the messaging menu entry looks like it sends the reply when it doesn't

[Nick Dedekind]

** Changed in: ubuntu-settings-components (Ubuntu)
   Importance: Undecided = High

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

Title:
  [Messaging Menu] Using enter in the messaging menu entry looks like
  it sends the reply when it doesn't

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Messaging App:
  Invalid
Status in Ubuntu UX bugs:
  Won't Fix
Status in indicator-messages package in Ubuntu:
  Invalid
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed

Bug description:
  Using rtm 169
  - receive a sms
  - read it in the messaging menu and decide to reply inline
  - enter something and hit return/enter on the osk

  - the text entry is dismissed and the osk hidden, it looks like the
  message was sent, where in fact it was not

  UX comment-

  We've added in the latest specification for the notification system
  the behaviour of the notification items in the messaging
  menu/notification centre. Link to the spec:
  
https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.aarksr1t9zhb

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

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

[Touch-packages] [Bug 1378469] Re: [Messaging Menu] should be closed after sending last message

[Nick Dedekind]

** Changed in: unity8 (Ubuntu)
 Assignee: Ying-Chun Liu (paulliu) = Nick Dedekind (nick-dedekind)

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

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

Title:
  [Messaging Menu] should be closed after sending last message

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  if you open the messaging-menu and reply to items in there, it should
  be closed automatically after replying to the last item.

  To reproduce:
  - send an sms to the phone
  - open the messaging-menu
  - reply to the message

  Expected results:
  - the menu should close

  Actual results:
  - a blank messaging-menu stays open, forcing user to close it

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

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

[Touch-packages] [Bug 1390136] Re: need a transition state for indicators reflecting laggy backends

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/ubuntu-system-settings/1390136
.laggy-backends

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

Title:
  need a transition state for indicators reflecting laggy backends

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged
Status in indicator-network source package in Utopic:
  Confirmed
Status in ubuntu-system-settings source package in Utopic:
  Confirmed
Status in indicator-network source package in Vivid:
  Fix Released
Status in ubuntu-system-settings source package in Vivid:
  Confirmed
Status in unity8 source package in Vivid:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  spawned from efforts in bug 1336715

  because the user's input toggle for airplane mode is both a reflection
  of user intent  the state of the backendand the backend is
  unfortunately variable  lengthy to change (anywhere from 1 to ~10+
  seconds sometimes) we need to have an intermediate/transition
  statee.g. toggle to airplane mode onthen animate somehow that
  there's a transition happening, until it either fails/succeeds

  comment from dizzypaty

  Between the user’s action of toggling the airplane switcher on and/or
  off and the backend updating the state, the indicator icon displayed
  on the statusbar should be the following: network-idle.svg

  
(https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk).

  
  Desired resolution

  Summary: the interface should immediately respond to user input
  confirming the action, even if the backend takes up to 20 seconds to
  actually change state.  Having the UI and backend out of sync for up
  to 30 seconds is not a problem, as long as it always goes back into
  sync after this delay.

  1.When the user changes the flight mode toggle switch it should
  instantly change state.

  2.The backend should then be informed of the state change.

  3.Up to 30 seconds later the backend completes the state change

  Note: The cellular connection indicator should always display the
  backend state, not the current flight mode toggle switch state

  
  Variation - user switches the flight mode toggle on and off rapidly.

  Once a flight mode state change request has been sent to the backend
  but before a conformation that the state change is complete is
  received, all further user interactions should be buffered on the
  client.  When the client receives conformation of the state change
  from the backend it should check to see if the state is in sync with
  its buffer.  If it is in sync nothing happens and the buffer is
  cleared.  If it is not in sync another state change signal is sent to
  the backend and the buffer is cleared.

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

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

[Touch-packages] [Bug 1436982] Re: Unity freezes for a few seconds when 'clear all' is tapped in Notifications

[Nick Dedekind]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Nick Dedekind (nick-dedekind)

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

Title:
  Unity freezes for a few seconds when 'clear all' is tapped in
  Notifications

Status in unity8 package in Ubuntu:
  New

Bug description:
  1. Create a missed call or sms.
  2. Open Notification from top.
  3. press the 'clear all' label
  4. try to close the Notification menu by dragging it from bottom

  What happens:
  Nothing happens, unity seem to freeze for 2 seconds.

  This issue does not exist in RTM branch.

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

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

[Touch-packages] [Bug 1390136] Re: need a transition state for indicators reflecting laggy backends

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/ubuntu-settings-components/1390136
.laggy-backends

** Branch linked: lp:~nick-dedekind/unity8/1390136.laggy-backends

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

Title:
  need a transition state for indicators reflecting laggy backends

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged
Status in indicator-network source package in Utopic:
  Confirmed
Status in ubuntu-system-settings source package in Utopic:
  Confirmed
Status in indicator-network source package in Vivid:
  Confirmed
Status in ubuntu-system-settings source package in Vivid:
  Confirmed
Status in unity8 source package in Vivid:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  New
Status in ubuntu-system-settings package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  spawned from efforts in bug 1336715

  because the user's input toggle for airplane mode is both a reflection
  of user intent  the state of the backendand the backend is
  unfortunately variable  lengthy to change (anywhere from 1 to ~10+
  seconds sometimes) we need to have an intermediate/transition
  statee.g. toggle to airplane mode onthen animate somehow that
  there's a transition happening, until it either fails/succeeds

  comment from dizzypaty

  Between the user’s action of toggling the airplane switcher on and/or
  off and the backend updating the state, the indicator icon displayed
  on the statusbar should be the following: network-idle.svg

  
(https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk).

  
  Desired resolution

  Summary: the interface should immediately respond to user input
  confirming the action, even if the backend takes up to 20 seconds to
  actually change state.  Having the UI and backend out of sync for up
  to 30 seconds is not a problem, as long as it always goes back into
  sync after this delay.

  1.When the user changes the flight mode toggle switch it should
  instantly change state.

  2.The backend should then be informed of the state change.

  3.Up to 30 seconds later the backend completes the state change

  Note: The cellular connection indicator should always display the
  backend state, not the current flight mode toggle switch state

  
  Variation - user switches the flight mode toggle on and off rapidly.

  Once a flight mode state change request has been sent to the backend
  but before a conformation that the state change is complete is
  received, all further user interactions should be buffered on the
  client.  When the client receives conformation of the state change
  from the backend it should check to see if the state is in sync with
  its buffer.  If it is in sync nothing happens and the buffer is
  cleared.  If it is not in sync another state change signal is sent to
  the backend and the buffer is cleared.

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

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

[Touch-packages] [Bug 1422883] Re: Support com.canonical.indicator.basic indicator type

[Nick Dedekind]

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

This is not a problem with the type, but only the icon which the list
item was using.

Same as: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1422835

** This bug has been marked a duplicate of bug 1422835
   Unity8 stucks in icon loading code

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

Title:
  Support com.canonical.indicator.basic indicator type

Status in unity8 package in Ubuntu:
  New

Bug description:
  If we use an indicator profile that causes an indicator (like
  indicator-power in the 'desktop' profile) to export a
  com.canonical.indicator.basic for the x-canonical-type hint, unity8
  freezes.

  It seems we don't have support for this indicator type yet.  And if we
  want to work with 'desktop' indicator profiles, we'll need to add
  support.

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

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

[Touch-packages] [Bug 1414025] Re: Call back and the phone icon don't work in messaging indicator

[Nick Dedekind]

** Changed in: unity8 (Ubuntu)
   Status: New = Confirmed

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

Title:
  Call back and the phone icon don't work in messaging indicator

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  With devel-proposed image 73 on mako, the call back button and the
  phone icon don't work. To reproduce:

  * produce a missed call on the phone by calling it and hanging up again
  * pull down messaging indicator
  * click on call back button

  = nothing happens

  * click on phone icon

  = nothing happens

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

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

[Touch-packages] [Bug 1414025] Re: Call back and the phone icon don't work in messaging indicator

[Nick Dedekind]

Problem was introduced in indicator-messages
13.10.1+15.04.20150112-0ubuntu1

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

** Changed in: unity8 (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: indicator-messages (Ubuntu)
   Importance: Undecided = Critical

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

Title:
  Call back and the phone icon don't work in messaging indicator

Status in indicator-messages package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  With devel-proposed image 73 on mako, the call back button and the
  phone icon don't work. To reproduce:

  * produce a missed call on the phone by calling it and hanging up again
  * pull down messaging indicator
  * click on call back button

  = nothing happens

  * click on phone icon

  = nothing happens

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

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

[Touch-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher

[Nick Dedekind]

@ted.
What work for the splash screen? As far as I am aware, there shouldn't be any 
splash screens for UI processes launched by a prompt helper.

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

Title:
  Media Player should not be visible in the app scope and launcher

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in mediaplayer-app package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  In Progress
Status in mediaplayer-app package in Ubuntu RTM:
  In Progress
Status in url-dispatcher package in Ubuntu RTM:
  In Progress

Bug description:
  The mediaplayer is an 'auxiliary app' in the current design approach.
  That means that its purpouse it playback media launched by other apps
  (e.g Messaging) or scopes (e.g. Videos). It should not be launched
  from the App scopes.

  However, the 'Update' section System Settings should still display it
  when an update to mediaplayer is available.

  Current behaviour
  - Mediaplayer app displayed in App Scope, Launcher and Settings

  Desired behaviour
  - Mediaplayer app not displayed in App Scope or Launcher
  - Mediaplayer displayed in Settings  Update

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

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

[Touch-packages] [Bug 1390136] Re: need a transition state for indicators reflecting laggy backends

[Nick Dedekind]

Hm, i didn't see the new description before I posted. Based on the new
one from John, it doesn't look like we need to change the API if we
don't need to track the transition.

The current method we use in Unity8 should suffice with a little tweaking. 
Currently we only wait 1.5 seconds for the server state to re-assert itself, 
which is why the switch flips out a bit if it takes longer.
Increasing this to 30 seconds, adding a currently in transition animation and 
buffering other changes until the state change is confirmed or 30 seconds is up 
should suffice.

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

Title:
  need a transition state for indicators reflecting laggy backends

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged
Status in indicator-network source package in Utopic:
  Confirmed
Status in ubuntu-system-settings source package in Utopic:
  Confirmed
Status in indicator-network source package in Vivid:
  Confirmed
Status in ubuntu-system-settings source package in Vivid:
  Confirmed
Status in unity8 source package in Vivid:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  New
Status in ubuntu-system-settings package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  spawned from efforts in bug 1336715

  because the user's input toggle for airplane mode is both a reflection
  of user intent  the state of the backendand the backend is
  unfortunately variable  lengthy to change (anywhere from 1 to ~10+
  seconds sometimes) we need to have an intermediate/transition
  statee.g. toggle to airplane mode onthen animate somehow that
  there's a transition happening, until it either fails/succeeds

  comment from dizzypaty

  Between the user’s action of toggling the airplane switcher on and/or
  off and the backend updating the state, the indicator icon displayed
  on the statusbar should be the following: network-idle.svg

  
(https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk).

  
  Desired resolution

  Summary: the interface should immediately respond to user input
  confirming the action, even if the backend takes up to 20 seconds to
  actually change state.  Having the UI and backend out of sync for up
  to 30 seconds is not a problem, as long as it always goes back into
  sync after this delay.

  1.When the user changes the flight mode toggle switch it should
  instantly change state.

  2.The backend should then be informed of the state change.

  3.Up to 30 seconds later the backend completes the state change

  Note: The cellular connection indicator should always display the
  backend state, not the current flight mode toggle switch state

  
  Variation - user switches the flight mode toggle on and off rapidly.

  Once a flight mode state change request has been sent to the backend
  but before a conformation that the state change is complete is
  received, all further user interactions should be buffered on the
  client.  When the client receives conformation of the state change
  from the backend it should check to see if the state is in sync with
  its buffer.  If it is in sync nothing happens and the buffer is
  cleared.  If it is not in sync another state change signal is sent to
  the backend and the buffer is cleared.

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

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

[Touch-packages] [Bug 1390136] Re: need a transition state for indicators reflecting laggy backends

[Nick Dedekind]

And while indicator-network waits for the flight mode change request to
be applied, it can change to the network-idle.svg icon.

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

Title:
  need a transition state for indicators reflecting laggy backends

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged
Status in indicator-network source package in Utopic:
  Confirmed
Status in ubuntu-system-settings source package in Utopic:
  Confirmed
Status in indicator-network source package in Vivid:
  Confirmed
Status in ubuntu-system-settings source package in Vivid:
  Confirmed
Status in unity8 source package in Vivid:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  New
Status in ubuntu-system-settings package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  spawned from efforts in bug 1336715

  because the user's input toggle for airplane mode is both a reflection
  of user intent  the state of the backendand the backend is
  unfortunately variable  lengthy to change (anywhere from 1 to ~10+
  seconds sometimes) we need to have an intermediate/transition
  statee.g. toggle to airplane mode onthen animate somehow that
  there's a transition happening, until it either fails/succeeds

  comment from dizzypaty

  Between the user’s action of toggling the airplane switcher on and/or
  off and the backend updating the state, the indicator icon displayed
  on the statusbar should be the following: network-idle.svg

  
(https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk).

  
  Desired resolution

  Summary: the interface should immediately respond to user input
  confirming the action, even if the backend takes up to 20 seconds to
  actually change state.  Having the UI and backend out of sync for up
  to 30 seconds is not a problem, as long as it always goes back into
  sync after this delay.

  1.When the user changes the flight mode toggle switch it should
  instantly change state.

  2.The backend should then be informed of the state change.

  3.Up to 30 seconds later the backend completes the state change

  Note: The cellular connection indicator should always display the
  backend state, not the current flight mode toggle switch state

  
  Variation - user switches the flight mode toggle on and off rapidly.

  Once a flight mode state change request has been sent to the backend
  but before a conformation that the state change is complete is
  received, all further user interactions should be buffered on the
  client.  When the client receives conformation of the state change
  from the backend it should check to see if the state is in sync with
  its buffer.  If it is in sync nothing happens and the buffer is
  cleared.  If it is not in sync another state change signal is sent to
  the backend and the buffer is cleared.

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

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

[Touch-packages] [Bug 1407720] Re: Panel uses incorrect serialisation for indicator-network menu icons

[Nick Dedekind]

the indicator-loader is supplied by libindicator3-tools.

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

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

** No longer affects: libindicator

** Changed in: unity8 (Ubuntu)
   Status: New = Invalid

** Summary changed:

- Panel uses incorrect serialisation for indicator-network menu icons
+ Indicator-loader uses incorrect serialisation for indicator-network menu icons

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

Title:
  Indicator-loader uses incorrect serialisation for indicator-network
  menu icons

Status in libindicator package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Currently indicator-network exports icons to show like this (gdbus
  dump):

  'icons': 
[
 ('themed', ['gsm-3g-full']),
 ('themed', ['nm-signal-50-secure'])
]
   ,

  That is they are an array of variants (that happen to be tuples).
  However this seems to be incorrect. At least if you use the indicator-
  loader it chokes on these and refuses to draw them. The form that it
  accepts looks like this:

  'icons': 
[
 ('themed', ['gsm-3g-full']),
 ('themed', ['simcard-locked']),
 ('themed', ['nm-signal-75-secure'])
]
   

  That is, an array of tuple variants. One of these two gets it wrong
  and since indicator-loader is the older of the two, I'm guessing that
  is the correct one. Feel free to reassign as appropriate if you feel
  that Unity8 is doing the right thing here.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/unity8/lp1378821.time-translation

-- 
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:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  Triaged

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 time 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

[Touch-packages] [Bug 1403458] [NEW] No persistent property for current screen status in com.canonical.Unity.Screen

[Nick Dedekind]

Public bug reported:

Unity8 needs to know the current screen status is when it starts.
Currently we only get the screen status changes (Off/On).

If unity8 starts when the screen is off, it takes we need to cycle the
state a few times to get the screen to come back on. This is because u8
defaults the status to On.

** Affects: unity-system-compositor
 Importance: Undecided
 Status: New

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

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

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

Title:
  No persistent property for current screen status in
  com.canonical.Unity.Screen

Status in Unity System Compositor:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 needs to know the current screen status is when it starts.
  Currently we only get the screen status changes (Off/On).

  If unity8 starts when the screen is off, it takes we need to cycle the
  state a few times to get the screen to come back on. This is because
  u8 defaults the status to On.

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

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

[Touch-packages] [Bug 1378469] Re: [Messaging Menu] should be closed after sending last message

[Nick Dedekind]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Ying-Chun Liu (paulliu)

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

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

Title:
  [Messaging Menu] should be closed after sending last message

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  if you open the messaging-menu and reply to items in there, it should
  be closed automatically after replying to the last item.

  To reproduce:
  - send an sms to the phone
  - open the messaging-menu
  - reply to the message

  Expected results:
  - the menu should close

  Actual results:
  - a blank messaging-menu stays open, forcing user to close it

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Nick Dedekind]

Currently in unity8 we rely on indicator-datetime translations for time
string formats; but since these are no longer in sync with the one's
used in unity8, it's not working.

I'm moving the time formatter into the sdk where the translations will be done.
Everything (messaging  alarm/events) should be passing around time stamps 
rather than time strings, which can be formatted  translated by the UIs 
inconsistently.

-- 
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:
  Invalid
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 1390136] Re: need a transition state for indicators reflecting laggy backends

[Nick Dedekind]

We're probably going to need a more complex mechanism for indicator related 
actions than what we have now if we want popups and such things.
At the moment we are using dbus modelled gactions; as far as i know, there is 
no feedback available for this as to indicating success/failure other than not 
changing the setting.

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

Title:
  need a transition state for indicators reflecting laggy backends

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-network package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged
Status in indicator-network source package in Utopic:
  New
Status in ubuntu-system-settings source package in Utopic:
  New
Status in indicator-network source package in Vivid:
  New
Status in ubuntu-system-settings source package in Vivid:
  New
Status in unity8 source package in Vivid:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  New
Status in ubuntu-system-settings package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  spawned from efforts in bug 1336715

  because the user's input toggle for airplane mode is both a reflection
  of user intent  the state of the backendand the backend is
  unfortunately variable  lengthy to change (anywhere from 1 to ~10+
  seconds sometimes) we need to have an intermediate/transition
  statee.g. toggle to airplane mode onthen animate somehow that
  there's a transition happening, until it either fails/succeeds

  comment from dizzypaty

  Between the user’s action of toggling the airplane switcher on and/or
  off and the backend updating the state, the indicator icon displayed
  on the statusbar should be the following: network-idle.svg

  
(https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk).

  
  Desired resolution

  Summary: the interface should immediately respond to user input
  confirming the action, even if the backend takes up to 20 seconds to
  actually change state.  Having the UI and backend out of sync for up
  to 30 seconds is not a problem, as long as it always goes back into
  sync after this delay.

  1.When the user changes the flight mode toggle switch it should
  instantly change state.

  2.The backend should then be informed of the state change.

  3.Up to 30 seconds later the backend completes the state change

  Note: The cellular connection indicator should always display the
  backend state, not the current flight mode toggle switch state

  
  Variation - user switches the flight mode toggle on and off rapidly.

  Once a flight mode state change request has been sent to the backend
  but before a conformation that the state change is complete is
  received, all further user interactions should be buffered on the
  client.  When the client receives conformation of the state change
  from the backend it should check to see if the state is in sync with
  its buffer.  If it is in sync nothing happens and the buffer is
  cleared.  If it is not in sync another state change signal is sent to
  the backend and the buffer is cleared.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Nick Dedekind]

This is due to the datetime indicator no longer having relative time
formatting; so the cross domain usage for translated time formats in
unity8 is no longer in sync.

Highlights the problem of inconsistency, and the need to move this to
sdk.

-- 
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 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/ubuntu-translations/+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 1390098] Re: Active call panel incorrectly displayed when recieving a call

[Nick Dedekind]

** Changed in: unity8 (Ubuntu)
   Status: Triaged = Invalid

** Changed in: unity8 (Ubuntu RTM)
   Status: Triaged = Invalid

-- 
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 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/dialer-app/+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 1390067] Re: Silent mode does not change the icon to the mute icon (or like)

[Nick Dedekind]

** Changed in: indicator-sound (Ubuntu)
 Assignee: (unassigned) = Nick Dedekind (nick-dedekind)

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

Title:
  Silent mode does not change the icon to the mute icon (or like)

Status in Sound Menu:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  Setting the phone on silent mode, the user should have some feedback
  to whether it is enabled from the panel icon. Currently we still show
  what volume the phone is set to.

  See https://wiki.ubuntu.com/Sound

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

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

[Touch-packages] [Bug 1384950] Re: Trusted prompts need to be part of the lifecycle

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/qtmir/1355173.trust-prompt-suspend

** Branch linked: lp:~nick-dedekind/mir/1355173.trust-prompt-suspend

** Branch linked: lp:~nick-dedekind/platform-api/1355173.trust-prompt-
suspend

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

Title:
  Trusted prompts need to be part of the lifecycle

Status in “pay-service” package in Ubuntu:
  New
Status in “trust-store” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  After we fix bug #1355173, we'll be leaking trusted prompts in the
  sense that when an app gets unfocused (and potentially killed
  subsequently), the trusted prompts will be left running, not suspended
  with the app. We should apply the same rules to the whole app
  container (can we use ual? add the prompts to the pgroup/cgroup?).

  This needs an escape route, too, for trusted helpers to be able to
  kill prompts as they need to.

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

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

[Touch-packages] [Bug 1355173] Re: Switching windows with a Trusted Prompt Session active loses the trusted prompt session

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/qtmir/1355173.trust-prompt-suspend

** Branch linked: lp:~nick-dedekind/mir/1355173.trust-prompt-suspend

** Branch linked: lp:~nick-dedekind/platform-api/1355173.trust-prompt-
suspend

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

Title:
  Switching windows with a Trusted Prompt Session active loses the
  trusted prompt session

Status in Qt integration with the Mir display server:
  In Progress
Status in Online Accounts setup for Ubuntu Touch:
  Invalid
Status in “pay-service” package in Ubuntu:
  New
Status in “qtmir” package in Ubuntu:
  New
Status in “trust-store” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Triaged
Status in “qtmir” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  Triaged

Bug description:
  
  When we create a trusted prompt session over an application, let's say a 
small dialog, and then switch applications, when we switch back to the original 
application the dialog is not overlayed on top of the original application. The 
program providing the dialog seems happy, and is still running, but visually it 
is not there.

  We notice this when using the payments UI which overlays ontop of the
  dash. In some cases we need to show Online Accounts which runs as an
  independent application and causes a switching behavior. When
  returning back to the dash the Payment UI is not visible. It also
  happens if the Payment UI is visible and you switch applications using
  the right swipe.

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

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

[Touch-packages] [Bug 1382078] Re: Revealed Indicators UI hides some indicators

[Nick Dedekind]

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

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

Title:
  Revealed Indicators UI hides some indicators

Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  The new indicator panel code (correctly) honors the indicators'
  visible flag when deciding what to hide from the status bar.

  However, it also (incorrectly) honors this flag in the Revealed
  Indicators UI. The RTM Usability Fixes document lists that all of our
  indicators should be visible there, regardless of whether they're
  hidden in the status bar.

  IIUC this was one of the original goals of the redesign -- to
  declutter the status bar without losing access to the lesser
  indicators

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

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

[Touch-packages] [Bug 1376201] Re: indicators not overshooting any more when scrolling

[Nick Dedekind]

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

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

Title:
  indicators not overshooting any more when scrolling

Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  Unlike the rest of the platform, the indicators don't overshoot any
  more when scrolling. This makes them feel different from the rest of
  unity...

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

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

[Touch-packages] [Bug 1391940] [NEW] Wifi switch does not follow enabling in system battery settings

[Nick Dedekind]

Public bug reported:

Switching wifi on/off from battery settings works with the actual
network, but the indicator switch does not seem to update.

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

** Package changed: indicator-network (Ubuntu) = indicator-network
(Ubuntu RTM)

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

Title:
  Wifi switch does not follow enabling in system battery settings

Status in “indicator-network” package in Ubuntu RTM:
  New

Bug description:
  Switching wifi on/off from battery settings works with the actual
  network, but the indicator switch does not seem to update.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Nick Dedekind]

I think the callIndicatorVisible flag should only be set if there are
active calls and if the live call window is not active or about to be.

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

Title:
  Active call panel incorrectly displayed when recieving a call

Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu RTM:
  Triaged

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/dialer-app/+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 1390098] Re: Active call panel incorrectly displayed when recieving a call

[Nick Dedekind]

So the reason is that when the user accepts a call, the live call window
takes a short while to load. Between accepting the call and the live
call window showing, the CallManager.callindicatorVisible flag is set,
which causes the active call hint to display. Then when the live call
shows, it is unset, which hides the active call hint in the panel.

I'm not sure that unity can manage this any more than it already does.

** Changed in: dialer-app
   Status: Incomplete = Confirmed

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

Title:
  Active call panel incorrectly displayed when recieving a call

Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu RTM:
  Triaged

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/dialer-app/+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 1390098] Re: Active call panel incorrectly displayed when recieving a call

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/dialer-app/lp1390098.active-call-
hint

** Changed in: dialer-app
 Assignee: Gustavo Pichorim Boiko (boiko) = Nick Dedekind (nick-dedekind)

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

Title:
  Active call panel incorrectly displayed when recieving a call

Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu RTM:
  Triaged

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/dialer-app/+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 1385331] Re: Notification LED stays on when no messages in notification center

[Nick Dedekind]

** Branch linked: lp:~nick-dedekind/unity8/lp1385331.led

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

Title:
  Notification LED stays on when no messages in notification center

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Observed the notification LED staying on even though there were no
  notifications in the indicators and the notification icon was greyed
  out.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Nick Dedekind]

** Branch unlinked: lp:~nick-dedekind/ubuntu-settings-
components/lp1336715.check.sync

-- 
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-system-settings” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Confirmed
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 1336715] Re: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings

[Nick Dedekind]

Believe the problem is fixed in indicators now.
The same binding bugs exist in the system settings now. I've added some generic 
components for switches/checkboxes to ubuntu-settings-components and a branch 
for ubuntu-system-settings to use them.

-- 
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-system-settings” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu RTM:
  New
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 1336715] Re: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings

[Nick Dedekind]

Test Case:
1) In USS languages page; set Spell checking to true then false.
2) phablet$ dconf write /com/canonical/keyboard/maliit/spell-checking true

Expected outcome: UI should update Spell checking value to true
Actual outcome: UI still displays false until page is closed and re-opened.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/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-system-settings” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu RTM:
  New
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 1352977] Re: Creating a prompt session for an app without a surface does not show the prompt

[Nick Dedekind]

** Changed in: qtmir
   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/1352977

Title:
  Creating a prompt session for an app without a surface does not show
  the prompt

Status in OSM app for Ubuntu Touch:
  New
Status in Qt integration with the Mir display server:
  Fix Released
Status in “location-service” package in Ubuntu:
  Fix Released

Bug description:
  Need to be able to show a prompt for an application which has not yet
  created a surface

  Use Case:
  osmtouch requests access to location-service before creating a window.

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

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