[Touch-packages] [Bug 1945111] [NEW] Switching proprietary drivers on a not up-to-date system breaks it badly

[Michael Zanetti]

Public bug reported:

When a system is not fully up to date, mainly when there's a kernel
update available, software-properties-gtk still allows to switch
drivers, for example switching between nvidia drivers.

Doing so will cause it to update the kernel, but not do a full upgrade.
After the operation software-properties-gtk will suggest to reboot the
machine and most likely cause the user to just do so.

The problem with that is that linux-modules-extras will not be installed
now and after the reboot the user is left with a broken system: Non-
functioning graphics (well, llvmpipe still does if lucky) and what's
even worse, no network drivers and depending on the machine maybe even
without input device support. This will cause the user to require a
second machine and a USB stick (and quite some knowledge) to recover the
system.

I've ran into this a couple of times now, seems reproducible. It is
quite tricky to get out of this which IMO makes this a somewhat critical
bug.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Switching proprietary drivers on a not up-to-date system breaks it
  badly

Status in software-properties package in Ubuntu:
  New

Bug description:
  When a system is not fully up to date, mainly when there's a kernel
  update available, software-properties-gtk still allows to switch
  drivers, for example switching between nvidia drivers.

  Doing so will cause it to update the kernel, but not do a full
  upgrade. After the operation software-properties-gtk will suggest to
  reboot the machine and most likely cause the user to just do so.

  The problem with that is that linux-modules-extras will not be
  installed now and after the reboot the user is left with a broken
  system: Non-functioning graphics (well, llvmpipe still does if lucky)
  and what's even worse, no network drivers and depending on the machine
  maybe even without input device support. This will cause the user to
  require a second machine and a USB stick (and quite some knowledge) to
  recover the system.

  I've ran into this a couple of times now, seems reproducible. It is
  quite tricky to get out of this which IMO makes this a somewhat
  critical bug.

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


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

[Touch-packages] [Bug 1506946] Re: Volume increases on its own when phone is muted.

[Michael Zanetti]

This is the same as https://bugs.launchpad.net/canonical-devices-system-
image/+bug/1478506

Not sure why that has been marked as duplicate of something different
tho.


What happens is that the system volume is changed every time an Audio {} or 
SoundEffect {} item is created.

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

Title:
  Volume increases on its own when phone is muted.

Status in indicator-sound package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm traveling with limited bandwidth and electricity so I lack the
  resources to investigate this much further today.

  Steps to reproduce:
  1. Put phone in silent mode
  2. Start playing "machines vs machines"
  3. Sound plays at full volume (don't know if this is, itself, a bug)
  4. Turn down volume and continue playing.

  Expected behavior: Volume stays silent
  Actual behavior:  Every 20 seconds or so, the volume will increase itself 
several levels

  Running rc-proposed on arale

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

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

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Michael Zanetti]

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

** Changed in: reminders-app (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  New
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - *All* Ubuntu.Components imports (including ListItems, Popups, Pickers,
    Theme, Styles etc.) should go to 1.3.
  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

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

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

[Touch-packages] [Bug 1389727] Re: Can't run any application using PositionSource on desktop

[Michael Zanetti]

** Description changed:

  Using this example code:
  
  
  import QtQuick 2.2
  import QtPositioning 5.1
  
  Item {
- height: 500; width: 500
+ height: 500; width: 500
  
- PositionSource {}
+ PositionSource {}
  }
  --
  
  crashes when started on desktop with the message:
  
  Ubuntu Platform API: Unable to find module configuration file -- Aborting
  Aborted (core dumped)
  
- 
- This affects all phone applications using Positioning. They can't be tested 
on the desktop atm.
+ This affects all phone applications using Positioning. They can't be
+ tested on the desktop atm. Each test run needs to happen on the phone,
+ which slows down the app development process a lot.

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

Title:
  Can't run any application using PositionSource on desktop

Status in Client Developer Experience:
  Confirmed
Status in platform-api:
  New
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Using this example code:

  
  import QtQuick 2.2
  import QtPositioning 5.1

  Item {
  height: 500; width: 500

  PositionSource {}
  }
  --

  crashes when started on desktop with the message:

  Ubuntu Platform API: Unable to find module configuration file -- Aborting
  Aborted (core dumped)

  This affects all phone applications using Positioning. They can't be
  tested on the desktop atm. Each test run needs to happen on the phone,
  which slows down the app development process a lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1389727/+subscriptions

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

[Touch-packages] [Bug 1510360] Re: maximize, close, launch goes full screen with no buttons

[Michael Zanetti]

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

** Branch linked: lp:~mzanetti/unity8/panel-button-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/1510360

Title:
  maximize, close, launch goes full screen with no buttons

Status in canonical-pocket-desktop:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  so i was testing for bug 1504269
  on nexus4
  last update: 2015-10-26 14:09:21
  version version: 54
  version ubuntu: 20151026
  version device: 20150911
  version custom: 20150929-2-vivid

  i had the mouse & keyboard connected, no external monitor
  i had dash & system settings open
  i maximized dash, then reset to windowed mode with same button
  i maximized u-s-s, then i accidentally hit "quit" button
  i relaunched u-s-s
  expected: to either launch back in window mode as maximized with buttons
  actual: launched in full screen, but as in phone mode - with no buttons

  noticed that subsequent launch of phone app (while in this state)
  first appeared as a full screen phone mode - but after blanking and
  using switcher, phone app went to windowed mode as expected, but u-s-s
  persisted in the state of phone mode full screen no buttons. launched
  a few other apps, all were in windowed mode.

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

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

[Touch-packages] [Bug 1510967] [NEW] Operating the OSK with mouse double-clicks buttons

[Michael Zanetti]

Public bug reported:

Pair a Bluetooth mouse with a phone but no keyboard. That will still
give you the OSK and allow typing things with the mouse on the OSK.
However, each button is pressed twice.

** Affects: ubuntu-keyboard
 Importance: Undecided
 Status: New

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

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

** Description changed:

- Pair a Bluetooth mouse with a phone but no Keyboard. That will still
+ Pair a Bluetooth mouse with a phone but no keyboard. That will still
  give you the OSK and allow typing things with the mouse on the OSK.
  However, each button is pressed twice.

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

Title:
  Operating the OSK with mouse double-clicks buttons

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

Bug description:
  Pair a Bluetooth mouse with a phone but no keyboard. That will still
  give you the OSK and allow typing things with the mouse on the OSK.
  However, each button is pressed twice.

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

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

[Touch-packages] [Bug 1510969] Re: Windows cannot be resized

[Michael Zanetti]

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  Windows cannot be resized

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  when in pocket pc mode windows with borders near the edges of the
  display cannot be resized without accessing the launcher or spread.

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

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

[Touch-packages] [Bug 1488146] Re: [Icons] window mode spread, no icon for dash

[Michael Zanetti]

@Matthieu, can you please attach the svg icon too, so I can generate all
the required sizes myself. Also other apps seem to ship the svg too.

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

Title:
  [Icons] window mode spread, no icon for dash

Status in Ubuntu UX:
  In Progress
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  when in windowed mode, invoke right edge spread (through swipe or mouse 
pressure)
  all launched apps have an icon, but dash is missing

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

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

[Touch-packages] [Bug 1510360] Re: maximize, close, launch goes full screen with no buttons

[Michael Zanetti]

@kevin, yes, the minimized apps not being restored when activated from
the spread is known and is fixed in

https://code.launchpad.net/~lukas-
kde/unity8/activateWindows/+merge/275706

This one didn't make it into the silo yet tho.

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

Title:
  maximize, close, launch goes full screen with no buttons

Status in canonical-pocket-desktop:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  so i was testing for bug 1504269
  on nexus4
  last update: 2015-10-26 14:09:21
  version version: 54
  version ubuntu: 20151026
  version device: 20150911
  version custom: 20150929-2-vivid

  i had the mouse & keyboard connected, no external monitor
  i had dash & system settings open
  i maximized dash, then reset to windowed mode with same button
  i maximized u-s-s, then i accidentally hit "quit" button
  i relaunched u-s-s
  expected: to either launch back in window mode as maximized with buttons
  actual: launched in full screen, but as in phone mode - with no buttons

  noticed that subsequent launch of phone app (while in this state)
  first appeared as a full screen phone mode - but after blanking and
  using switcher, phone app went to windowed mode as expected, but u-s-s
  persisted in the state of phone mode full screen no buttons. launched
  a few other apps, all were in windowed mode.

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

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

[Touch-packages] [Bug 1438465] Re: A window dragged under the panel can't be dragged out again

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

** 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/1438465

Title:
  A window dragged under the panel can't be dragged out again

Status in canonical-pocket-desktop:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  so many times,when i drag the window to the top, the max-min-button
  will be overlaied by panel,so i can not drag this window back and i
  can not see these buttons

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

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

[Touch-packages] [Bug 1438465] Re: A window dragged under the panel can't be dragged out again

[Michael Zanetti]

The linked branch prevents windows to be dragged under the panel by
dragging on the title bar. In case a window should still end up under
the panel (might happen on alt+drag eventually as commnt #3 points out)
it will be positioned below the panel when it's closed and reopened.
Except from the not yet supported alt+drag in unity8, this seems to
reflect unity7's behavior.

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

Title:
  A window dragged under the panel can't be dragged out again

Status in canonical-pocket-desktop:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  so many times,when i drag the window to the top, the max-min-button
  will be overlaied by panel,so i can not drag this window back and i
  can not see these buttons

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

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

[Touch-packages] [Bug 1488146] Re: [Icons] window mode spread, no icon for dash

[Michael Zanetti]

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

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

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

Title:
  [Icons] window mode spread, no icon for dash

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  when in windowed mode, invoke right edge spread (through swipe or mouse 
pressure)
  all launched apps have an icon, but dash is missing

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

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

[Touch-packages] [Bug 1354374] Re: [wm] foreground app not unfocused when indicators open

[Michael Zanetti]

I'm not sure if this is something we really want... Opening some
indicator on unity7 doesn't unfocus the current app either. Also the use
case for the indicators is to quickly pull them down, change a single
setting and dismiss them again *without* interrupting the current
task/app.

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

Title:
  [wm] foreground app not unfocused when indicators open

Status in unity8 package in Ubuntu:
  New

Bug description:
  Open a game like dropping letters. Start a game playing. Now open the
  indicators bar. Game keeps playing even while obscured by the
  indicators.

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

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

[Touch-packages] [Bug 1512430] Re: Shouldn't be able to swipe away incoming call notification

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: Michał Sawicz (saviq) => Lukáš Tinkl (lukas-kde)

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

Title:
  Shouldn't be able to swipe away incoming call notification

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

Bug description:
  latest rc-proposed on krillin
   
  Steps to reproduce:
  1) lock phone
  2) call phone
  3) press volume down button to lower the volume, this causes sound 
notification to be shown and incoming call notification to be reduced in height
  4) while incoming call notification reduced in height, swipe it from left to 
right

  Expected results:
  incoming call notification should not be dismissed, so you can still answer 
the phone

  Actual results:
  incoming call notification is dismissed and you now have no way to answer the 
incoming call

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

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

[Touch-packages] [Bug 1497097] Re: [enhancement] Add non-linear animation progress (e.g. a sigmoid function) for minimize/maximize

[Michael Zanetti]

The linked branch uses UbuntuNumberAnimations as per Vesa's comment.

Animations will be refined when desing specs them out. For now I think
this bug can be closed as the linked branch addresses the reporter's
issue and it's an improvement over current trunk already.

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

Title:
  [enhancement] Add non-linear animation progress (e.g. a sigmoid
  function) for minimize/maximize

Status in canonical-pocket-desktop:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  [enhancement] Add non-linear animation progress (e.g. a sigmoid
  function).

  The current linear animations for minimize/maximize look kind of
  awkward and unnatural.

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

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

[Touch-packages] [Bug 1512683] [NEW] moving the mouse doesn't wake up the screen

[Michael Zanetti]

Public bug reported:

With a Bluetooth mouse connected, when the device locks the screen,
moving the mouse should wake the screen up.

** Affects: canonical-pocket-desktop
 Importance: Undecided
 Status: New

** Affects: unity-system-compositor
 Importance: Undecided
 Status: New

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

** Also affects: unity-system-compositor
   Importance: Undecided
   Status: New

** Also affects: canonical-pocket-desktop
   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/1512683

Title:
  moving the mouse doesn't wake up the screen

Status in canonical-pocket-desktop:
  New
Status in Unity System Compositor:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  With a Bluetooth mouse connected, when the device locks the screen,
  moving the mouse should wake the screen up.

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

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

[Touch-packages] [Bug 1513003] [NEW] AdaptivePageLayout doesn't allow hiding a Page header

[Michael Zanetti]

Public bug reported:

Trying to port reminders-app to use an APL instead of my home-brew
multicolumn thing, I noticed that it's no longer possible to hide a
Page's header using:

head {
  visible: false
  locked: true
}


This was hiding the page header successfully with a PageStack, however, inside 
an AdaptivePageLayout it doesn't work any more.

** 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/1513003

Title:
  AdaptivePageLayout doesn't allow hiding a Page header

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

Bug description:
  Trying to port reminders-app to use an APL instead of my home-brew
  multicolumn thing, I noticed that it's no longer possible to hide a
  Page's header using:

  head {
visible: false
locked: true
  }

  
  This was hiding the page header successfully with a PageStack, however, 
inside an AdaptivePageLayout it doesn't work any more.

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

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

[Touch-packages] [Bug 1513047] Re: spread delegates are using clipping

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

Title:
  spread delegates are using clipping

Status in unity8 package in Ubuntu:
  New

Bug description:
  It appears that app windows are turning on clipping when the spread is
  opened. This is really inefficient graphically because it is a
  transformed rectangle and so Qt falls back to stencil-based clipping.
  We should avoid clipping in this case at all cost

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

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

[Touch-packages] [Bug 1513047] Re: spread delegates are using clipping

[Michael Zanetti]

Well, the clipping is required by design. That said, I agree using QML
clipping there is not good enough and needs to be improved. Back then
when the spread was implemented, MirSurfaceItem didn't support cropping
yet, so this way of clipping had to be used.

The solution for this bug is to move to MirSurfaceItem's surface
cropping mechanism and drop the QML based clipping.

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

Title:
  spread delegates are using clipping

Status in unity8 package in Ubuntu:
  New

Bug description:
  It appears that app windows are turning on clipping when the spread is
  opened. This is really inefficient graphically because it is a
  transformed rectangle and so Qt falls back to stencil-based clipping.
  We should avoid clipping in this case at all cost

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

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

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

[Michael Zanetti]

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

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

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

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Triaged

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

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

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

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

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

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

[Touch-packages] [Bug 1395313] Re: PositionSource ignores configuration proerties

[Michael Zanetti]

** Also affects: canonical-developer-experience
   Importance: Undecided
   Status: New

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

Title:
  PositionSource ignores configuration proerties

Status in Client Developer Experience:
  New
Status in location-service:
  New
Status in qtlocation-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  The properties "active" and "updateInterval" don't have any effect on
  Ubuntu. Despite PositionSource.active being set to false, it keeps on
  emitting position updates and does not regard the updateInterval
  setting as well. Updates appear in random intervals.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1395313/+subscriptions

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

[Touch-packages] [Bug 1420169] Re: Alarms don't set RTC alarm to wake up the phone

[Michael Zanetti]

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

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

Title:
  Alarms don't set RTC alarm to wake up the phone

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The alarms API is not setting the device's RTC alarm to power on the
  phone when an alarm should ring and the device is powered off.

  This causes alarms to be lost.

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

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

[Touch-packages] [Bug 1513450] Re: higher than expected cpu for unity8

[Michael Zanetti]

Some observations:

* For me, this happens only when the Bluetooth page in systemsettings is opened.
* Doesn't matter if windowed or staged mode
* Happens on all devices

turns out the Bluetooth Page in systemsettings is animating 3
ActivityIndicators even when they are not visible.

Not sure how that causes unity8's CPU usage to be that high, but the
linked ubuntu-system-settings branch improves the situation a lot.

However, given that the ActivityIndicators are invisible, we probably
should investigate why they keep on triggering rendering updates.

Adding ubuntu-system-settings, qtmir and qtubuntu.

** Branch linked: lp:~mzanetti/ubuntu-system-settings/only-animate-when-
visible

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

** Also affects: ubuntu-system-settings-online-accounts
   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/1513450

Title:
  higher than expected cpu for unity8

Status in canonical-pocket-desktop:
  New
Status in QtMir:
  New
Status in Online Accounts setup for Ubuntu Touch:
  New
Status in Ubuntu UI Toolkit:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  running in window mode, open u-s-s, run top
  unity8 running at ~40% cpu on N7 cpu freq ~1GHz

  no monitor attached

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

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

[Touch-packages] [Bug 1513450] Re: higher than expected cpu for unity8

[Michael Zanetti]

Perhaps the UITK should be added to. The ActivityIndicator should not
calculate the animations all the when visible is false.

Marking unity8 as invalid as this is what it takes to constantly render
an animated app surface. It might be improved in QtMir, but not much
that unity8 can do about it.

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

** Also affects: ubuntu-ui-toolkit
   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/1513450

Title:
  higher than expected cpu for unity8

Status in canonical-pocket-desktop:
  New
Status in QtMir:
  New
Status in Online Accounts setup for Ubuntu Touch:
  New
Status in Ubuntu UI Toolkit:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  running in window mode, open u-s-s, run top
  unity8 running at ~40% cpu on N7 cpu freq ~1GHz

  no monitor attached

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

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

[Touch-packages] [Bug 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false

[Michael Zanetti]

** Summary changed:

- higher than expected cpu for unity8
+ ActivityIndicators cause very high cpu usage for unity8/mir even when 
visible: false

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

Title:
  ActivityIndicators cause very high cpu usage for unity8/mir even when
  visible: false

Status in canonical-pocket-desktop:
  New
Status in Mir:
  New
Status in QtMir:
  New
Status in Online Accounts setup for Ubuntu Touch:
  New
Status in Ubuntu UI Toolkit:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  running in window mode, open u-s-s, run top
  unity8 running at ~40% cpu on N7 cpu freq ~1GHz

  no monitor attached

  note: testing with silo 18 of mir containing
  lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17)

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

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

[Touch-packages] [Bug 1511020] Re: [Pocket PC] fullscreen video isn't full screen

[Michael Zanetti]

Indeed, Olivier is right. This is not fully implemented in Windowed
mode.

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

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

Title:
  [Pocket PC] fullscreen video isn't full screen

Status in unity8 package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  using the web browser on a pocket pc youtube videos don't go full
  screen. see attached image.

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

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

[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update

[Michael Zanetti]

FWIW, this affects the Logviewer app in the store too.

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

Title:
  Font in Terminal is incorrectly massive since recent update

Status in Canonical System Image:
  New
Status in Ubuntu Terminal App:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Last know good image: 166
  Changes on 167: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog
  Landing request for Unity8/Mir: 
https://requests.ci-train.ubuntu.com/#/ticket/564

  After updating my Nexus 4 and Krillin over the weekend I notice the
  terminal now has really huge text. Even dialling down the font size in
  the app to 8pt results in huge unusable text.

  Before:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png
  After:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png

  With the same font size setting on both.

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

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

[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update

[Michael Zanetti]

Here's the terminal app:

http://bazaar.launchpad.net/~ubuntu-terminal-dev/ubuntu-terminal-
app/reboot/view/head:/src/plugin/qmltermwidget/lib/qtermwidget.cpp#L281

One thing that I've overlooked in the previous comment is that it uses
"font.pointSize", not font.pixelSize. Same for the terminal app. That
should indeed be correct.

So seems to be an issue in the calculation of font's pointSize after
all.Sorry for the wrong assessment in the previous comment.

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

Title:
  Font in Terminal is incorrectly massive since recent update

Status in Canonical System Image:
  New
Status in Ubuntu Terminal App:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Last know good image: 166
  Changes on 167: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog
  Landing request for Unity8/Mir: 
https://requests.ci-train.ubuntu.com/#/ticket/564

  After updating my Nexus 4 and Krillin over the weekend I notice the
  terminal now has really huge text. Even dialling down the font size in
  the app to 8pt results in huge unusable text.

  Before:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png
  After:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png

  With the same font size setting on both.

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

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

[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update

[Michael Zanetti]

Here's the line of code in the logviewer app that is responsible for it:

http://bazaar.launchpad.net/~vtuson/logviewer/trunk/view/head:/app/ui/LogPage.qml#L183

Indeed, it does hardcode the font size to a pixel value. So while I
confirm something has changed recently, it seems to reveal improper use
of components in apps instead of real breakage in the system.

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

Title:
  Font in Terminal is incorrectly massive since recent update

Status in Canonical System Image:
  New
Status in Ubuntu Terminal App:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Last know good image: 166
  Changes on 167: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog
  Landing request for Unity8/Mir: 
https://requests.ci-train.ubuntu.com/#/ticket/564

  After updating my Nexus 4 and Krillin over the weekend I notice the
  terminal now has really huge text. Even dialling down the font size in
  the app to 8pt results in huge unusable text.

  Before:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png
  After:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png

  With the same font size setting on both.

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Michael Zanetti]

** Package changed: unity8 (Ubuntu RTM) => qtbase-opensource-src
(Ubuntu)

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

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  Triaged
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1515921] Re: 2 mouse pointers when running gedit with gtk mir on Unity8

[Michael Zanetti]

Adding Libertine as I think we want to keep unity8's cursor and hide
compiz' one.

Please reopen for unity8 if I'm wrong.

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

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

** Also affects: canonical-pocket-desktop
   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/1515921

Title:
  2 mouse pointers when running gedit with gtk mir on Unity8

Status in canonical-pocket-desktop:
  New
Status in Libertine:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  ubuntu 16.04 
  i get 2 mouse pointers when running gedit with gtk mir on Unity8. they also 
have diff sizes and positions. even after closing gedit i'm left with 2 mouse 
pointers. i don't need 2, one is enough. it gets really confusing using 2 mouse 
pointers at the same time, uh

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

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

[Touch-packages] [Bug 1515977] Re: Shell rotates inappropriately in windowed mode

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  Shell rotates inappropriately in windowed mode

Status in unity8 package in Ubuntu:
  New

Bug description:
  Install latest rc proposed on a nexus 4. 
  Attach a bluetooth mouse - this triggers windowed mode.
  Orient device in landscape
  Open weather app - which is locked portrait in the .desktop file

  Shell rotates to become portrait and there's no way to get it out of
  that mode easily.

  The shell should probably ignore the .desktop setting which says that
  an app is portrait only if it's windowed.

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

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

[Touch-packages] [Bug 1516272] Re: Bluetooth keyboard doesn't count as activity, screen locks while typing!

[Michael Zanetti]

** Also affects: unity-system-compositor
   Importance: Undecided
   Status: New

** Also affects: canonical-pocket-desktop
   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/1516272

Title:
  Bluetooth keyboard doesn't count as activity, screen locks while
  typing!

Status in canonical-pocket-desktop:
  New
Status in Unity System Compositor:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Bluetooth mouse movement clears "idle" flag, but Bluetooth keyboard
  does not... so if you use a bluetooth keyboard to type for more than a
  few minutes the screen will blank

  Tested in r162 14/11/15

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

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

[Touch-packages] [Bug 1516653] Re: OSK inputs each key twice on external screen

[Michael Zanetti]

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

** This bug has been marked a duplicate of bug 1451554
   Every key is pressed twice on the desktop

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

Title:
  OSK inputs each key twice on external screen

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

Bug description:
  Using Nexus 4 with Slimport-HDMI cable and bluetooth mouse. Anything I
  type on the OSK results in two characters for a single one.

  Example: Unlock then device. Type "correct horse battery staple". The
  resulting input will be "ccoorreecctt  hhoorrssee  bbaaeerryy
  ssttaappllee" and it's impossible to unlock.

  Example: Performa a search via the browser's URL bar. Type "grumpy
  cat". It will search for "ggrruummppyy  ccaatt".

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

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

[Touch-packages] [Bug 1451554] Re: Every key is pressed twice on the desktop

[Michael Zanetti]

** Also affects: canonical-pocket-desktop
   Importance: Undecided
   Status: New

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

Title:
  Every key is pressed twice on the desktop

Status in canonical-pocket-desktop:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  If I launch an app with QT_IM_MODULE=MaliitPhablet system-settings, every key 
is pressed twice.
  Pressing h - a - l - l -o -  gives me:
  'Hhaaoo. '

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-keyboard 0.99.trunk.phablet2+15.04.20150326-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  4 21:43:00 2015
  InstallationDate: Installed on 2014-10-10 (206 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140922)
  SourcePackage: ubuntu-keyboard
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2015-01-02 (122 days ago)

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

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

[Touch-packages] [Bug 1515921] Re: 2 mouse pointers when running gedit with gtk mir on Unity8

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  2 mouse pointers when running gedit with gtk mir on Unity8

Status in canonical-pocket-desktop:
  New
Status in Libertine:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04 
  i get 2 mouse pointers when running gedit with gtk mir on Unity8. they also 
have diff sizes and positions. even after closing gedit i'm left with 2 mouse 
pointers. i don't need 2, one is enough. it gets really confusing using 2 mouse 
pointers at the same time, uh

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

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

[Touch-packages] [Bug 1517571] Re: Unity8 is crashing under UITK tests

[Michael Zanetti]

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

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

Title:
  Unity8 is crashing under UITK tests

Status in qtmir package in Ubuntu:
  New

Bug description:
  unity8 - 8.11+15.04.2
  UITK - 
1.3.1717+201511171416-staging-0+1.3.1688+15.10.20151018.1~ubuntu15.04.1 (but 
the stock Overlay version does the same)

  Install ubuntu-ui-toolkit-autopilot on the device and run

  $ phablet-test-run
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

  or on the device

  $ autopilot3 run
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

  The shell will crash and restart with this output from the test tools
  ->

  [1447868985.090179]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/mir-AHj2eT/mir-0.17.1+15.04.20151105.1/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  Failed to create screencast
  Failed to connect to server. Error was :Failed to connect to server socket: 
Connection refused
  g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  /bin/bash: line 1: 3796 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 
run ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

  
  The `apport-bug unity8` gave this ->

  The problem cannot be reported:
  This is not an official Ubuntu package. Please remove any third party package 
and try again.

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

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

[Touch-packages] [Bug 1518395] Re: Cursor no longer appears in unity8 desktop

[Michael Zanetti]

same on vivid + overlay

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  Cursor no longer appears in unity8 desktop

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The latest Xenial unity8 release (8.11+16.04.20151112.1-0ubuntu1)
  breaks the cursor on the desktop.  No cursor is seen on the unity8
  greeter, so I can't log in.

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

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

[Touch-packages] [Bug 1518395] Re: Cursor no longer appears in unity8 desktop

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) => Michael Zanetti (mzanetti)

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

Title:
  Cursor no longer appears in unity8 desktop

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  The latest Xenial unity8 release (8.11+16.04.20151112.1-0ubuntu1)
  breaks the cursor on the desktop.  No cursor is seen on the unity8
  greeter, so I can't log in.

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

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

[Touch-packages] [Bug 1500633] Re: orientation sensor "last vertical" seems to be remembered and applied

[Michael Zanetti]

This sounds like the expected behavior if you ask me...

The sensors have a threshold so they don't keep on flipping between
portrait/landscape when the device is flat on the table. If you hold it
in portrait and place it flat on the desk it will stay in portrait, if
you hold it in landscape and then place it flat down, it'll stay in
landscape.  In unity8 we don't read actual sensor values ourselves, but
we get a clear "Landscape" or "Portrait" from the lower layers (qtmir I
think fills in the Screen.orientation value).

The above steps to reproduce do this:

* Put sensors in Portrait
* place it down flat (sensors stay in portrait as expected)
* focus a rotation-locked application which will cause unity8 to ignore the 
sensors.
* put the sensors in landscape
* place it down flat (sensors stay in landscape as expected)
* focus a rotation-enabled app, which will cause unity8 to regard the sensors, 
and thus rotate to landscape.

In order to get away with it, it seems a back-channel from unity8 down
to QtMir and QtUbuntu would be needed in order to really turn off the
sensor logic while a rotation-locked app is focused. I for one still
think the way it currently works is quite expected tho. After all you
did hold it up in portrait and instructed the sensors to rotate to
portrait. Unity8 will execute that request as soon as possible.

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

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

Title:
  orientation sensor "last vertical" seems to be remembered and applied

Status in QtMir:
  Incomplete
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  latest rc-image

  1. download and install machines vs machines
  2. open machines vs machines
  3. open browser, rotate to landscape
  4. lay flat on table so that browser is still in landscape
  5. switch back to machines vs machines with launcher
  6. raise top of phone as to make the phone vertical in portrait, lay back 
down flat
  7. switch to browser

  expected: browser would be in landscape
  actual: browser rotates

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

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

[Touch-packages] [Bug 1494442] Re: Turn crash generation off by default for phone on stable channel

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

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

Title:
  Turn crash generation off by default for phone on stable channel

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  To avoid UI freezes and perceptions of slowness, we would like to turn
  this option off by default for consumers, but leave it on for
  developers and in the proposed channels.

  Once bug #1437633 is fixed, we can put "manual" in the
  whoopsie.override file

  Not sure how to do this conditionally just for stable

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

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

[Touch-packages] [Bug 1474225] Re: Screen rotates itself to landscape when the phone is laying on the desk

[Michael Zanetti]

So what's happening here is that you tell the sensors that the phone
would be in landscape position (by shaking it), but you have an app
focused which forces the shell to stick with portrait. Then, you start
an app that supports landscape and unity will do what you asked it for,
rotating to landscape.

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

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

Title:
  Screen rotates itself to landscape when the phone is laying on the
  desk

Status in qtubuntu-sensors:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Screen rotates itself to landscape when the phone is laying on the
  desk.

  I might be mistaken but this bug seems to be a new issue that arrived
  with the full shell rotation feature in wily. Using a phone while it's
  laying flat on the desk it sometimes rotates itself to landscape.

  Seems like we might have some over-sensitive accelerometer logic.

  $ system-image-cli -i
  current build number: 255
  device name: mako
  channel: ubuntu-touch/devel-proposed/ubuntu
  last update: 2015-07-14 03:41:29
  version version: 255
  version ubuntu: 20150714
  version device: 20150708
  version custom: 20150714

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtubuntu-sensors/+bug/1474225/+subscriptions

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

[Touch-packages] [Bug 1367459] Re: Messaging app should not rotate upside down

[Michael Zanetti]

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

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

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

Title:
  Messaging app should not rotate upside down

Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The messaging app should not rotate upside down.
  This can be confuse, and in some cases causes problems  for example the user 
can try to answer a call in the incorrect position.

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

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

[Touch-packages] [Bug 1474225] Re: Screen rotates itself to landscape when the phone is laying on the desk

[Michael Zanetti]

there is thresholding in the sensors... which is exactly the cause of
this "bug".

When shaking, you make the threshold switch to landscape and by putting
it flat down on the desk you keep it that way, not allowing the
threshold to be hit to switch back to landscape. You just don't see it,
because you're using an app that forces locked to portrait (the dash for
example). As soon as you allow unity to rotate (by launching the
settings app) it will catch up with what the sensors state is =>
landscape.


Now, one way to get around the situation would be to disable the sensors while 
unity is locked to some orientation. This however seems quite tricky, as on one 
hand that would need to be synced with what sensors tell apps, but also apps 
might still want to know the physical orientation even though locked to some 
orientation.

IMO this is working as expected, even though I agree it can cause some
oddities like unintentional shaking. But in the end it's really what you
tell the device to do. As an analogy, you're sort of asking for a
mechanism to distinguish accidental display taps from intentional ones.

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

Title:
  Screen rotates itself to landscape when the phone is laying on the
  desk

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

Bug description:
  Screen rotates itself to landscape when the phone is laying on the
  desk.

  I might be mistaken but this bug seems to be a new issue that arrived
  with the full shell rotation feature in wily. Using a phone while it's
  laying flat on the desk it sometimes rotates itself to landscape.

  Seems like we might have some over-sensitive accelerometer logic.

  $ system-image-cli -i
  current build number: 255
  device name: mako
  channel: ubuntu-touch/devel-proposed/ubuntu
  last update: 2015-07-14 03:41:29
  version version: 255
  version ubuntu: 20150714
  version device: 20150708
  version custom: 20150714

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtubuntu-sensors/+bug/1474225/+subscriptions

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

[Touch-packages] [Bug 1497750] Re: dbus-daemon uses huge amount of CPU

[Michael Zanetti]

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

** This bug has been marked a duplicate of bug 1480877
   Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

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

Title:
  dbus-daemon uses huge amount of CPU

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  dbus-daemon is working all the time on ubuntu phone, using up to 100%
  CPU. It seems that some services are emitting messages continuously,
  particularly  Upstart and network indicator. The phone becomes
  unusable and must be restarted to work

  Disabling wifi reduces a lot the amount of messages

  Phone : BQ Aquaris E4.5 Ubuntu Edition
  DistroRelease: Ubuntu 15.04 (r25)
  Uname: Linux ubuntu-phablet 3.4.67

  extract from dbus--monitor --profile --session (lots of messages
  without actually using the phone)

  sig   1442761291  858477  83609   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761291  877536  83610   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761292  667180  83611   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761292  722328  1416/com/canonical/indicator/power  
org.gtk.Actions Changed
  sig   1442761292  760751  83612   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761292  764403  83613   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761292  768329  83614   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761295  884397  6118/com/canonical/indicator/network
org.gtk.Actions Changed
  sig   1442761295  905577  83615   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761295  907594  83616   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761300  773941  1417/com/canonical/indicator/power  
org.gtk.Actions Changed
  sig   1442761300  781362  83617   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761300  782578  83618   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761306  862983  83619   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted
  sig   1442761306  882480  83620   /com/ubuntu/Upstart 
com.ubuntu.Upstart0_6   EventEmitted

  
  lots of messages are concerning access points
  Extract from dbus--monitor  --session

  signal sender=:1.58 -> dest=(null destination) serial=6139 
path=/com/canonical/indicator/network; interface=org.gtk.Actions; member=Changed
     array [
     ]
     array [
     ]
     array [
    dict entry(
   string "accesspoint.1259::strength"
   variant byte 59
    )
     ]
     array [
     ]
  signal sender=:1.0 -> dest=(null destination) serial=83772 
path=/com/ubuntu/Upstart; interface=com.ubuntu.Upstart0_6; member=EventEmitted
     string "dbus"
     array [
    string "SIGNAL=Changed"
    string "BUS=session"
    string "INTERFACE=org.gtk.Actions"
    string "OBJPATH=/com/canonical/indicator/network"
    string "SENDER=:1.58"
     ]
  signal sender=:1.0 -> dest=(null destination) serial=83773 
path=/com/ubuntu/Upstart; interface=com.ubuntu.Upstart0_6; member=EventEmitted
     string "dbus"
     array [
    string "SIGNAL=PropertiesChanged"
    string "BUS=system"
    string "INTERFACE=org.freedesktop.NetworkManager.AccessPoint"
    string "OBJPATH=/org/freedesktop/NetworkManager/AccessPoint/2913"
    string "SENDER=:1.7"
     ]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Sun Sep 20 16:40:39 2015
  InstallationDate: Installed on 2015-08-25 (25 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150825-170536)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1503901] Re: Authenticator app won't open with latest SDK

[Michael Zanetti]

Ok. Turns out the issue here is that authenticator does this:

Layout {
  ...
  Label {
Button {
}
  }
}

Reason for doing that is that the cell-size of the label should be what
the label's implicitSize is. When the app starts up, the label is to be
covered by a button tho. Placing a button inside a label makes it crash
since the latest update. Here's a standalone example how to reproduce
it:

http://paste.ubuntu.com/12712857/

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

Title:
  Authenticator app won't open with latest SDK

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The Authenticator app in the store won't open on latest rc-proposed
  images.  I'm assuming something in the SDK changed out from under it.
  Nothing useful in the log though.

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

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

[Touch-packages] [Bug 1504057] [NEW] Bluetooth icon should turn blue when there's traffic happening

[Michael Zanetti]

Public bug reported:

The Bluetooth  icon in the panel is currently an outline icon when
Bluetooth is turned on but nothing is connected, it will turn to the
filled icon when something connects. Additionally it would be useful if
the icon would turn blue when there is actual traffic happening. This is
something I've been used to from previous phones and it helps greatly to
identify the state of the connection. For instance, the Music player
playing music to a Bluetooth headset would be immediately visible when
you've put the headset away already and forgot to stop the music player.

Also, it causes bug reports of failed connections to be more detailed as
this gives details to the developer whether the connection failed when
establishing the ACL link or if something failed after a profile has
been connected already.

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

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

Title:
  Bluetooth icon should turn blue when there's traffic happening

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  The Bluetooth  icon in the panel is currently an outline icon when
  Bluetooth is turned on but nothing is connected, it will turn to the
  filled icon when something connects. Additionally it would be useful
  if the icon would turn blue when there is actual traffic happening.
  This is something I've been used to from previous phones and it helps
  greatly to identify the state of the connection. For instance, the
  Music player playing music to a Bluetooth headset would be immediately
  visible when you've put the headset away already and forgot to stop
  the music player.

  Also, it causes bug reports of failed connections to be more detailed
  as this gives details to the developer whether the connection failed
  when establishing the ACL link or if something failed after a profile
  has been connected already.

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

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

[Touch-packages] [Bug 1504084] [NEW] Websites show mobile version, even on desktop

[Michael Zanetti]

Public bug reported:

On unity8 on desktop, the webbrowser-app shows the mobile version of
websites. This can be reproduced with e.g. http://github.com

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

** Attachment added: "github.png"
   https://bugs.launchpad.net/bugs/1504084/+attachment/4488458/+files/github.png

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

Title:
  Websites show mobile version, even on desktop

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  On unity8 on desktop, the webbrowser-app shows the mobile version of
  websites. This can be reproduced with e.g. http://github.com

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

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

[Touch-packages] [Bug 1504100] [NEW] Logging in google drive causes a mail "New log in from Android"

[Michael Zanetti]

Public bug reported:

I've logged in my google drive using the webbrowser-app on unity8. This
caused an email in my inbox with the following warning: "New sign-in
from Android"

See attached screenshot for details

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

** Attachment added: "New sign-in from Android - Inbox - 
michael_zane...@gmx.net - Mozilla Thunderbird_071.png"
   
https://bugs.launchpad.net/bugs/1504100/+attachment/4488489/+files/New%20sign-in%20from%20Android%20-%20Inbox%20-%20michael_zanetti%40gmx.net%20-%20Mozilla%20Thunderbird_071.png

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

Title:
  Logging in google drive causes a mail "New log in from Android"

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  I've logged in my google drive using the webbrowser-app on unity8.
  This caused an email in my inbox with the following warning: "New
  sign-in from Android"

  See attached screenshot for details

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

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

[Touch-packages] [Bug 1504065] Re: Cannot play videos when a wired headphone is connected

[Michael Zanetti]

rc-proposed. reproduced the issue on flo and krillin

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

Title:
  Cannot play videos when a wired headphone is connected

Status in The Sound Menu:
  New
Status in mediaplayer-app:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When having a wired headset connected to the device, video playback
  keeps on being paused as soon as playback is started. Looks like some
  snap-decision notification is shown, but it's too short time to read
  what it actually says because it disappears again when the playback
  stops again.

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

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

[Touch-packages] [Bug 1504065] Re: Cannot play videos when a wired headphone is connected

[Michael Zanetti]

The build numbers are completely useless as they are independent per
channel & device. Just flash the latest rc-proposed on any device of
your choice and see this happening

Here's the build number for my krillin in case you still think they're
useful: 146

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

Title:
  Cannot play videos when a wired headphone is connected

Status in The Sound Menu:
  New
Status in mediaplayer-app:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When having a wired headset connected to the device, video playback
  keeps on being paused as soon as playback is started. Looks like some
  snap-decision notification is shown, but it's too short time to read
  what it actually says because it disappears again when the playback
  stops again.

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

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

[Touch-packages] [Bug 1504269] Re: Dash loses minimize & fullscreen toggle buttons in windowed mode when put into full screen

[Michael Zanetti]

** Branch linked: lp:~mzanetti/unity8/panel-button-fixes

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

** 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/1504269

Title:
  Dash loses minimize & fullscreen toggle buttons in windowed mode when
  put into full screen

Status in canonical-pocket-desktop:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  testing on flo, the dash loses it's minimize & fullscreen toggle buttons in 
windowed mode when put into full screen
  makes it impossible to put it back to something "other than full screen" or 
minimize

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

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

[Touch-packages] [Bug 1504318] Re: power off dialog pops up instantly in window mode

[Michael Zanetti]

This seems to be a case for the DeviceConfiguration. While I agree that
what Kevin describes is the expected thing on a pocket desktop, what the
current implementation does is the expected thing on a regular PC. You
want to see the Power menu when pressing the power menu there.

Casing the decision based on the known phone/tablet models from
DeviceConfiguration should do, at least until design comes up with
something better.

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

Title:
  power off dialog pops up instantly in window mode

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

Bug description:
  happens on n7 and n4, ubuntu and ubuntu-pd

  steps, connect mouse, go into window mode
  strike power button to blank screen
  result you'll see the power off dialog come up immediately (before even 
blanking)
  expected - screen blank and unblank as normal with no display of the power 
off dialog

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

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

[Touch-packages] [Bug 1388070] Re: [Alarms] Allow snoozing an alarm by turning the phone.

[Michael Zanetti]

I don't think this has anything to do with the proximity sensor, also
not screen blanking...

this bug is about using the gyroscope sensor to snooze an alarm...

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

Title:
  [Alarms] Allow snoozing an alarm by turning the phone.

Status in Ubuntu UX:
  Fix Committed
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  It'd be great to allow snoozing alarms using the "turnover" gesture as
  described here:

  http://qt-project.org/doc/qt-5/sensorgesture-plugins-topics.html

  (Same goes for silenting incoming calls)

   UX comment 

  Please refer to the Screen blanking policy doc for further
  information:
  
https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0/edit?usp=sharing

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

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

[Touch-packages] [Bug 1388070] Re: [Alarms] Allow snoozing an alarm by turning the phone.

[Michael Zanetti]

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

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

Title:
  [Alarms] Allow snoozing an alarm by turning the phone.

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

Bug description:
  It'd be great to allow snoozing alarms using the "turnover" gesture as
  described here:

  http://qt-project.org/doc/qt-5/sensorgesture-plugins-topics.html

  (Same goes for silenting incoming calls)

   UX comment 

  Please refer to the Screen blanking policy doc for further
  information:
  
https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0/edit?usp=sharing

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

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

[Touch-packages] [Bug 1388070] Re: [Alarms] Allow snoozing an alarm by turning the phone.

[Michael Zanetti]

fwiw, this can't be added by 3rd party apps... needs to be done in
unity8 (also not in the clock app)

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

Title:
  [Alarms] Allow snoozing an alarm by turning the phone.

Status in Ubuntu UX:
  Fix Committed
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  It'd be great to allow snoozing alarms using the "turnover" gesture as
  described here:

  http://qt-project.org/doc/qt-5/sensorgesture-plugins-topics.html

  (Same goes for silenting incoming calls)

   UX comment 

  Please refer to the Screen blanking policy doc for further
  information:
  
https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0/edit?usp=sharing

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

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

[Touch-packages] [Bug 1453546] [NEW] cannot use color:/// uri for scope header foreground and divider color

[Michael Zanetti]

Public bug reported:

Creating a scope, I noticed that the color:/// uri notation only works
for PageHeader.Background, but it doesn't work for
PageHeader.ForegroundColor or PageHeader.DividerColor.

** 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/1453546

Title:
  cannot use color:/// uri for scope header foreground and divider color

Status in unity8 package in Ubuntu:
  New

Bug description:
  Creating a scope, I noticed that the color:/// uri notation only works
  for PageHeader.Background, but it doesn't work for
  PageHeader.ForegroundColor or PageHeader.DividerColor.

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

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

[Touch-packages] [Bug 1453546] Re: cannot use color:/// uri for scope header foreground and divider color

[Michael Zanetti]

IIUC, this docs say it should work, yes:
https://developer.ubuntu.com/en/scopes/guides/scopes-customization-
branding/

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

Title:
  cannot use color:/// uri for scope header foreground and divider color

Status in unity8 package in Ubuntu:
  New

Bug description:
  Creating a scope, I noticed that the color:/// uri notation only works
  for PageHeader.Background, but it doesn't work for
  PageHeader.ForegroundColor or PageHeader.DividerColor.

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

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

[Touch-packages] [Bug 1413801] Re: TextField's placeHolderText invisible inside a dialog

[Michael Zanetti]

Screenshot: http://i.imgur.com/Pma8cs6.png

Note, the two visible labels have manually set the color to "black".

Here's the code for the dialog: http://paste.ubuntu.com/11077309/

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

Title:
  TextField's placeHolderText invisible inside a dialog

Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  Using a dark background in an application, a Dialog and a TextField
  inside that Dialog renders the placeholderText nearly invisible.

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

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

[Touch-packages] [Bug 1331952] Re: [setup] UI language should follow SIM card preferred language

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Andrea Cimitan (cimi)

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

Title:
  [setup] UI language should follow SIM card preferred language

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

Bug description:
  Test steps:
  1. Insert a SIM card with preferred language Finnish
  2. Boot the phone
  Expected result: UI language is Finnish
  Actual result: UI language is English. Finnish or other languages can be 
manually selected from the settings UI.

  The SIM card's list of preferred languages is correctly given by oFono:
  dbus-send --print-reply --system --dest=org.ofono /ril_0 
org.ofono.SimManager.GetProperties

dict entry(
   string "PreferredLanguages"
   variant array [
 string "fi"
 string "sv"
 string "en"
  ]
)

  A technical reference is ETSI TS 102 221, section 13.3 EF_PL
  (Preferred Languages). But this is also a business requirement for OEM
  and operator partners.

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

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

[Touch-packages] [Bug 1453820] Re: App selection broken (select after Right-To-Left Swipe)

[Michael Zanetti]

Hello Ruben, thanks for the bug report. Does this happen all the time
for you? When it happens again, could you please check if it is really
only the right edge spread? Do that by locking and unlocking the screen
with the power button and then try swiping the greeter from right to
left. Does that still work?

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

Title:
  App selection broken (select after Right-To-Left Swipe)

Status in unity8 package in Ubuntu:
  New

Bug description:
  Device: BQ Aquaris 4.5
  Version: Ubuntu 14.10 R21
  OTA Version

  Describtion: 
  When doing right to left swipe shows running apps. The list should be 
scrollable by swiping and the apps should be focusable by touching its image 
from that list.

  Expectation:
  When swiping the running App list, the list should scroll the bitmaps of 
actual running apps. When touching an App from that list, that App should get 
focused and activated. When swiping an App image up or down, the App should get 
killed.

  Observation:
  Listing is not movable by swiping. When trying to scroll/swipe through list, 
the last application is focused.
  It is not possible to close apps by swiping up/down an App image.
  Switching the Apps by selecting App Icons in the Unity launcher is working as 
expected. Apps are responsive and working as expected.
  Swipe left to right works as expected, phone switches to formner App.

  UseCase:
  Was viewing calendar app. Then trying to switch to other app. Phone keeps in 
that state

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

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

[Touch-packages] [Bug 1454711] [NEW] unity8 crash with many random touch points

[Michael Zanetti]

Public bug reported:

I've just put my flat hand onto arale's screen and unity8 crashed. Turns
out I could reproduce this quite easily and managed to capture a trace:
http://paste.ubuntu.com/3929/

** Affects: unity8 (Ubuntu)
 Importance: Critical
 Assignee: Daniel d'Andrada (dandrader)
 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/1454711

Title:
  unity8 crash with many random touch points

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've just put my flat hand onto arale's screen and unity8 crashed.
  Turns out I could reproduce this quite easily and managed to capture a
  trace: http://paste.ubuntu.com/3929/

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

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

[Touch-packages] [Bug 1454711] Re: unity8 crash with many random touch points

[Michael Zanetti]

** Attachment added: "Video reproducing the bug"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1454711/+attachment/4396831/+files/video20150513_155830006.mp4

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

Title:
  unity8 crash with many random touch points

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've just put my flat hand onto arale's screen and unity8 crashed.
  Turns out I could reproduce this quite easily and managed to capture a
  trace: http://paste.ubuntu.com/3929/

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

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

[Touch-packages] [Bug 1454711] Re: unity8 crash with many random touch points

[Michael Zanetti]

Unlikely it's a dupe.

The fix for bug #1437357 was released to revision
0.4.4+15.04.20150511.1-0ubuntu1. I do have that one installed.

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

Title:
  unity8 crash with many random touch points

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've just put my flat hand onto arale's screen and unity8 crashed.
  Turns out I could reproduce this quite easily and managed to capture a
  trace: http://paste.ubuntu.com/3929/

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

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

[Touch-packages] [Bug 1455107] Re: Creating and destroying SoundEffects causes crashes

[Michael Zanetti]

** Project changed: media-hub => pulseaudio

** Description changed:

  I keep on receiving bug reports about Machines vs. Machines being crashy
- and I tracked it down to the SoundEffect item. When playing without
- sound effects enabled, the game seems very stable.
+ on Ubuntu Phones and I tracked it down to the SoundEffect item. When
+ playing without sound effects enabled, the game seems very stable.
  
  To get to the bottom of this I created an app that simulates a bit how a
  game works with sound effects. It's a bit more aggressive than Machines-
  vs-Machines (still not really far fetched from a real game scenario) and
  reliably triggers some crashers in less than a minute here.
  
  So far I've seen crashes in creating SoundEffects items as well as
  removing them from the scene.
  
  Please find the example here: lp:~mzanetti/+junk/soundcrasher
  
  You should be able to run it on any vivid powered device by just opening
  the .pro file in QtCreator and hit the play button. The logs vary a lot
  between crashes. Sometimes I get some PulseAudio messages, sometimes it
  just crashes without any. Probably some raciness. Anyhow, this example
  app should be give the system a hard time and reveal most of the crashes
  eventually.

** Project changed: pulseaudio => pulseaudio (Ubuntu)

** Tags added: bq

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Canonical Phone Foundations 
(canonical-phonedations-team)

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

Title:
  Creating and destroying SoundEffects causes crashes

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I keep on receiving bug reports about Machines vs. Machines being
  crashy on Ubuntu Phones and I tracked it down to the SoundEffect item.
  When playing without sound effects enabled, the game seems very
  stable.

  To get to the bottom of this I created an app that simulates a bit how
  a game works with sound effects. It's a bit more aggressive than
  Machines-vs-Machines (still not really far fetched from a real game
  scenario) and reliably triggers some crashers in less than a minute
  here.

  So far I've seen crashes in creating SoundEffects items as well as
  removing them from the scene.

  Please find the example here: lp:~mzanetti/+junk/soundcrasher

  You should be able to run it on any vivid powered device by just
  opening the .pro file in QtCreator and hit the play button. The logs
  vary a lot between crashes. Sometimes I get some PulseAudio messages,
  sometimes it just crashes without any. Probably some raciness. Anyhow,
  this example app should be give the system a hard time and reveal most
  of the crashes eventually.

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

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

[Touch-packages] [Bug 1455406] [NEW] Search history popover displaced when OSK opens

[Michael Zanetti]

Public bug reported:

With a vivid based image, do a search in the dash. Clear it, start a
second one (the popover should appear). When the OSK comes up, the
popver is displaced, being partly off-screen, and covering the input
field.

** Affects: unity8 (Ubuntu)
 Importance: High
 Assignee: Albert Astals Cid (aacid)
 Status: New

** Description changed:

  With a vivid based image, do a search in the dash. Clear it, start a
- second one (the popver should appear). When the OSK comes up, the popver
- is displaced, being partly off-screen, and covering the input field.
+ second one (the popover should appear). When the OSK comes up, the
+ popver is displaced, being partly off-screen, and covering the input
+ field.

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

Title:
  Search history popover displaced when OSK opens

Status in unity8 package in Ubuntu:
  New

Bug description:
  With a vivid based image, do a search in the dash. Clear it, start a
  second one (the popover should appear). When the OSK comes up, the
  popver is displaced, being partly off-screen, and covering the input
  field.

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

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

[Touch-packages] [Bug 1455107] Re: Creating and destroying SoundEffects causes crashes

[Michael Zanetti]

** Description changed:

  I keep on receiving bug reports about Machines vs. Machines being crashy
  on Ubuntu Phones and I tracked it down to the SoundEffect item. When
  playing without sound effects enabled, the game seems very stable.
  
  To get to the bottom of this I created an app that simulates a bit how a
  game works with sound effects. It's a bit more aggressive than Machines-
  vs-Machines (still not really far fetched from a real game scenario) and
  reliably triggers some crashers in less than a minute here.
  
  So far I've seen crashes in creating SoundEffects items as well as
  removing them from the scene.
  
  Please find the example here: lp:~mzanetti/+junk/soundcrasher
  
  You should be able to run it on any vivid powered device by just opening
  the .pro file in QtCreator and hit the play button. The logs vary a lot
  between crashes. Sometimes I get some PulseAudio messages, sometimes it
  just crashes without any. Probably some raciness. Anyhow, this example
- app should be give the system a hard time and reveal most of the crashes
+ app should give the system a hard time and reveal most of the crashes
  eventually.

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

Title:
  Creating and destroying SoundEffects causes crashes

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in qtmultimedia-opensource-src package in Ubuntu:
  New

Bug description:
  I keep on receiving bug reports about Machines vs. Machines being
  crashy on Ubuntu Phones and I tracked it down to the SoundEffect item.
  When playing without sound effects enabled, the game seems very
  stable.

  To get to the bottom of this I created an app that simulates a bit how
  a game works with sound effects. It's a bit more aggressive than
  Machines-vs-Machines (still not really far fetched from a real game
  scenario) and reliably triggers some crashers in less than a minute
  here.

  So far I've seen crashes in creating SoundEffects items as well as
  removing them from the scene.

  Please find the example here: lp:~mzanetti/+junk/soundcrasher

  You should be able to run it on any vivid powered device by just
  opening the .pro file in QtCreator and hit the play button. The logs
  vary a lot between crashes. Sometimes I get some PulseAudio messages,
  sometimes it just crashes without any. Probably some raciness. Anyhow,
  this example app should give the system a hard time and reveal most of
  the crashes eventually.

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

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

[Touch-packages] [Bug 1455567] [NEW] UbuntuShape fails to antialias when created while device is in landscape

[Michael Zanetti]

Public bug reported:

Steps to reproduce:

* flash latest vivid image
* open the gallery
* rotate device to landscape
* pull in the launcher from above

=> see how launcher icons are not antialiased
http://i.imgur.com/dh40r0N.png


Or another way:

* Open some random app
* Rotate the device to landscape
* using the right edge spread (now at the bottom) switch to the dash

=> see how all dash icons are not antialiased

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Loïc Molinari (loic.molinari)
 Status: In Progress

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

Title:
  UbuntuShape fails to antialias when created while device is in
  landscape

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

Bug description:
  Steps to reproduce:

  * flash latest vivid image
  * open the gallery
  * rotate device to landscape
  * pull in the launcher from above

  => see how launcher icons are not antialiased
  http://i.imgur.com/dh40r0N.png

  
  Or another way:

  * Open some random app
  * Rotate the device to landscape
  * using the right edge spread (now at the bottom) switch to the dash

  => see how all dash icons are not antialiased

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

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

[Touch-packages] [Bug 1445572] Re: [Right edge] Apps closing shouldn't be possible during the edge gesture

[Michael Zanetti]

** 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/1445572

Title:
  [Right edge] Apps closing shouldn't be possible during the edge
  gesture

Status in Ubuntu UX bugs:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to repro:

  - Open few apps
  - start right edge gesture 
  - during the gesture (while moving towards left and still holding finger 
down) interact with the spread items with another finger. For example try to 
swipe up or down to close.

  Result:
  - sometimes you can swipe an app to close it. sometimes the whole spread 
animation breaks.

  Expected result: 
  - The spread items can't be interacted with during the edge gesture. The 
items should be interactive only after user has finished the gesture by 
releasing the finger.

  ---
  Desired design: Expected result

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

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

[Touch-packages] [Bug 1459142] Re: Oxide 1.7 makes Unity8 qml tests not pass in a chroot

[Michael Zanetti]

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

** Project changed: unity8 => unity8 (Ubuntu)

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

** Changed in: oxide
   Status: New => Opinion

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

Title:
  Oxide 1.7 makes Unity8 qml tests not pass in a chroot

Status in Oxide Webview:
  Opinion
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  When using oxide 1.5.5-0ubuntu1 as shipped in vivid the qml tests of
  unity8 pass just fine.

  When using oxide 1.7.8-0ubuntu0.15.04.1 the test for the wizard hangs
  and says

  [0527/073908:FATAL:setuid_sandbox_client.cc(126)] Check failed:
  IsFileSystemAccessDenied().

  The backtrace of the hang is http://paste.ubuntu.com/11386907/

  Example of the hang happening in https://jenkins.qa.ubuntu.com/job
  /unity-phablet-qmluitests-wily/29/console

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

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

[Touch-packages] [Bug 1457129] Re: All sound stops playing after receiving SMS messages

[Michael Zanetti]

So this indicates the QtMultimedia backend (libaalmediaplayer.so) is
throwing an exception which is originating in libmedia-hub-client.so.3.

QML can't deal with exceptions (in C++ terms) and will inevitably crash.
As exceptions are not used in Qt by design, no QML module should ever
throw them.

Seems like there are two things to do here:

1) add a global try/catch somewhere to libaalmediaplayer.so to never throw 
exceptions up towards unity as there is no way for us to catch them.
2) fix this particular issue in libmedia-hub-client.so.3

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

Title:
  All sound stops playing after receiving SMS messages

Status in the base for Ubuntu mobile products:
  Confirmed
Status in media-hub package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing on Arale, build 6, vivid proposed

  Steps to reproduce (not that easy)
  1) goto System Settings->Sounds and set Message Received Sound to Xylo and 
check on "Vibrate with message sound" and "Vibrate in Silent Mode"
  1A) Lock the phone
  2) Send phone a bunch of text messages (like 4 in a row quickly)
  3) verify that sound is played, vibration is heard, and notification is 
displayed
  4) now open messaging app to the thread that received the message
  5) lock the phone
  6) Repeat steps 2 and 3, eventually the sounds stop playing and the 
notifications don't get displayed anymore, but the screen does light up.

  At this point media hub is hung and you can't plays sounds from
  anywhere, even music player

  (gdb) t a a bt

  Thread 15 (Thread 0xb2f3a3a0 (LWP 2186)):
  #0  0xb424f6b4 in ?? ()
  #1  0xb4263c8c in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 14 (Thread 0xb25ff3a0 (LWP 2187)):
  #0  0xb424f6b4 in ?? ()
  #1  0xb4263c8c in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 13 (Thread 0xb1bff3a0 (LWP 2189)):
  #0  0xb6320132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0x00149850 in boost::asio::detail::epoll_reactor::run(bool, 
boost::asio::detail::op_queue&) 
()
  #2  0x0014ab1a in 
boost::asio::detail::task_io_service::run(boost::system::error_code&) ()
  #3  0x00148c8e in _start ()

  Thread 12 (Thread 0xad3fe3a0 (LWP 2191)):
  #0  0xb63194e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0x in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 11 (Thread 0xacbfe3a0 (LWP 2192)):
  #0  0xb63194e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0x in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 10 (Thread 0xabcff3a0 (LWP 2202)):
  #0  0xb6387d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb6385980 in __lll_lock_wait () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb638119e in pthread_mutex_lock () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #3  0x001a8bc8 in ?? ()
  #4  0x001b21d6 in 
core::ubuntu::media::PlayerImplementation::Private::request_power_state()
 ()
  #5  0x001b5384 in 
core::ubuntu::media::PlayerImplementation::Private::make_state_change_handler()::{lambda(core::ubuntu::media::Engine::State
 const&)#1}::operator()(core::ubuntu::media::Engine::State const&) const ()
  ---Type  to continue, or q  to quit---
  #6  0x001b0c9a in std::_Function_handler >::_M_invoke(std::_Any_data 
const&, core::ubuntu::media::Engine::State) ()
  #7  0x001cf730 in 
core::Signal::operator()(core::ubuntu::media::Engine::State)
 ()
  #8  0x001cc2c2 in gstreamer::Engine::play() ()
  #9  0x001b2018 in 
core::ubuntu::media::PlayerImplementation::play()
 ()
  #10 0x001d87b8 in 
core::ubuntu::media::PlayerSkeleton::Private::handle_play(std::shared_ptr
 const&) ()
  #11 0xb6f161c0 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #12 0xb6245aa2 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 9 (Thread 0xa31ff3a0 (LWP 4024)):
  #0  0xb6387d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb638595c in __lll_lock_wait () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb638119e in pthread_mutex_lock () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #3  0x001a887e in ?? ()
  #4  0x001ac772 in std::_Function_handler const&), void 
core::dbus::Object::invoke_method_asynchronously_with_callback(std::function const&)>, 
std::string const&)::{lambda(std::shared_ptr 
const&)#1}>::_M_invoke(std::_Any_data const&, 
std::shared_ptr const&) ()
  #5  0xb6f17da4 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #6  0x001acc5a in void 
core::dbus::Object::invoke_method_asynchronously_with_callback(std::function const&)>, 
std::string const&) 

[Touch-packages] [Bug 1457129] Re: All sound stops playing after receiving SMS messages

[Michael Zanetti]

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

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

Title:
  All sound stops playing after receiving SMS messages

Status in the base for Ubuntu mobile products:
  Confirmed
Status in media-hub package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Testing on Arale, build 6, vivid proposed

  Steps to reproduce (not that easy)
  1) goto System Settings->Sounds and set Message Received Sound to Xylo and 
check on "Vibrate with message sound" and "Vibrate in Silent Mode"
  1A) Lock the phone
  2) Send phone a bunch of text messages (like 4 in a row quickly)
  3) verify that sound is played, vibration is heard, and notification is 
displayed
  4) now open messaging app to the thread that received the message
  5) lock the phone
  6) Repeat steps 2 and 3, eventually the sounds stop playing and the 
notifications don't get displayed anymore, but the screen does light up.

  At this point media hub is hung and you can't plays sounds from
  anywhere, even music player

  (gdb) t a a bt

  Thread 15 (Thread 0xb2f3a3a0 (LWP 2186)):
  #0  0xb424f6b4 in ?? ()
  #1  0xb4263c8c in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 14 (Thread 0xb25ff3a0 (LWP 2187)):
  #0  0xb424f6b4 in ?? ()
  #1  0xb4263c8c in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 13 (Thread 0xb1bff3a0 (LWP 2189)):
  #0  0xb6320132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0x00149850 in boost::asio::detail::epoll_reactor::run(bool, 
boost::asio::detail::op_queue&) 
()
  #2  0x0014ab1a in 
boost::asio::detail::task_io_service::run(boost::system::error_code&) ()
  #3  0x00148c8e in _start ()

  Thread 12 (Thread 0xad3fe3a0 (LWP 2191)):
  #0  0xb63194e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0x in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 11 (Thread 0xacbfe3a0 (LWP 2192)):
  #0  0xb63194e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0x in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 10 (Thread 0xabcff3a0 (LWP 2202)):
  #0  0xb6387d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb6385980 in __lll_lock_wait () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb638119e in pthread_mutex_lock () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #3  0x001a8bc8 in ?? ()
  #4  0x001b21d6 in 
core::ubuntu::media::PlayerImplementation::Private::request_power_state()
 ()
  #5  0x001b5384 in 
core::ubuntu::media::PlayerImplementation::Private::make_state_change_handler()::{lambda(core::ubuntu::media::Engine::State
 const&)#1}::operator()(core::ubuntu::media::Engine::State const&) const ()
  ---Type  to continue, or q  to quit---
  #6  0x001b0c9a in std::_Function_handler >::_M_invoke(std::_Any_data 
const&, core::ubuntu::media::Engine::State) ()
  #7  0x001cf730 in 
core::Signal::operator()(core::ubuntu::media::Engine::State)
 ()
  #8  0x001cc2c2 in gstreamer::Engine::play() ()
  #9  0x001b2018 in 
core::ubuntu::media::PlayerImplementation::play()
 ()
  #10 0x001d87b8 in 
core::ubuntu::media::PlayerSkeleton::Private::handle_play(std::shared_ptr
 const&) ()
  #11 0xb6f161c0 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #12 0xb6245aa2 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 9 (Thread 0xa31ff3a0 (LWP 4024)):
  #0  0xb6387d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb638595c in __lll_lock_wait () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb638119e in pthread_mutex_lock () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #3  0x001a887e in ?? ()
  #4  0x001ac772 in std::_Function_handler const&), void 
core::dbus::Object::invoke_method_asynchronously_with_callback(std::function const&)>, 
std::string const&)::{lambda(std::shared_ptr 
const&)#1}>::_M_invoke(std::_Any_data const&, 
std::shared_ptr const&) ()
  #5  0xb6f17da4 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #6  0x001acc5a in void 
core::dbus::Object::invoke_method_asynchronously_with_callback(std::function const&)>, 
std::string const&) ()
  #7  0x001a8ad4 in ?? ()
  #8  0x001b230e in 
core::ubuntu::media::PlayerImplementation::Private::clear_wakelock(core::ubuntu::media::PlayerImplementation::Private::wakelock_clear_t
 const&) ()
  #9  0x001b8052 in std::_Function_handler::Private::make_clear_wakelock_functor()::{lambda()#1}>::_M_invoke(std::_Any_data
 const&) ()
  #10 0x001b24da in 
std::thread::_Impl>(int, bool, std::function&&)::{lambda()#1} ()> >::_M_run() ()
  #11 0xb643f2a0 in ?? () from /usr/lib/arm-

[Touch-packages] [Bug 1459121] Re: phone unlock screen

[Michael Zanetti]

This can be reproduced by setting screen brightness to a minimum and
turning off the screen. Also happens on auto brightness and when being
in a dark place.

Seems the minimum supplied power for the display needs to be increased
for tiny bit.

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

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

** Summary changed:

- phone unlock screen
+ Screen doesn't wake up when on minimum brightness

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

Title:
  Screen doesn't wake up when on minimum brightness

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

Bug description:
  ubuntu 15.04 for phones beta r.223 (bq aquaris ubuntu edition)

  Since r.222 upgrade i noticed that sometimes I cant unlock the phone.
  When i push unlock button (one time) looks like nothing happens, screen 
doesn't woke up.
  If i press a second time  screen woke up for half second showing unlock 
screen.

  When it happens, i know that the OS is running because when i push the
  unlock button(first time), i can make a screen shot pushing up volume
  and down volume at same time it also reproduce the sound.

  Looks that the only problem is to wakeup the screen.

  It began to happen without install any program, just upgrades.
  When it happened to me I think that I haven't opened any app.

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

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

[Touch-packages] [Bug 1459121] Re: Screen doesn't wake up when on minimum brightness

[Michael Zanetti]

I just upgraded to the latest vivid image and cannot reproduce this any
more.

Josué, can you confirm this is fixed after upgrading?

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

Title:
  Screen doesn't wake up when on minimum brightness

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

Bug description:
  ubuntu 15.04 for phones beta r.223 (bq aquaris ubuntu edition)

  Since r.222 upgrade i noticed that sometimes I cant unlock the phone.
  When i push unlock button (one time) looks like nothing happens, screen 
doesn't woke up.
  If i press a second time  screen woke up for half second showing unlock 
screen.

  When it happens, i know that the OS is running because when i push the
  unlock button(first time), i can make a screen shot pushing up volume
  and down volume at same time it also reproduce the sound.

  Looks that the only problem is to wakeup the screen.

  It began to happen without install any program, just upgrades.
  When it happened to me I think that I haven't opened any app.

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

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

[Touch-packages] [Bug 1459121] Re: Screen doesn't wake up when on minimum brightness

[Michael Zanetti]

Yes. I also saw it some days ago for the first time. But since today's
update it's gone again for me.

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

Title:
  Screen doesn't wake up when on minimum brightness

Status in the base for Ubuntu mobile products:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  ubuntu 15.04 for phones beta r.223 (bq aquaris ubuntu edition)

  Since r.222 upgrade i noticed that sometimes I cant unlock the phone.
  When i push unlock button (one time) looks like nothing happens, screen 
doesn't woke up.
  If i press a second time  screen woke up for half second showing unlock 
screen.

  When it happens, i know that the OS is running because when i push the
  unlock button(first time), i can make a screen shot pushing up volume
  and down volume at same time it also reproduce the sound.

  Looks that the only problem is to wakeup the screen.

  It began to happen without install any program, just upgrades.
  When it happened to me I think that I haven't opened any app.

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

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

[Touch-packages] [Bug 1459121] Re: Screen doesn't wake up when on minimum brightness

[Michael Zanetti]

It was r17 on channel ubuntu-touch/rc-proposed/bq-aquaris.en. Now it's
r18.

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

Title:
  Screen doesn't wake up when on minimum brightness

Status in the base for Ubuntu mobile products:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  ubuntu 15.04 for phones beta r.223 (bq aquaris ubuntu edition)

  Since r.222 upgrade i noticed that sometimes I cant unlock the phone.
  When i push unlock button (one time) looks like nothing happens, screen 
doesn't woke up.
  If i press a second time  screen woke up for half second showing unlock 
screen.

  When it happens, i know that the OS is running because when i push the
  unlock button(first time), i can make a screen shot pushing up volume
  and down volume at same time it also reproduce the sound.

  Looks that the only problem is to wakeup the screen.

  It began to happen without install any program, just upgrades.
  When it happened to me I think that I haven't opened any app.

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

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

[Touch-packages] [Bug 1378267] Re: Suspended app screenshots are blurry

[Michael Zanetti]

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

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

Title:
  Suspended app screenshots are blurry

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

Bug description:
  It's really obvious that an app has been suspended when I switch to it
  and the screengrab is really blurry. Would be really nice if it wasn't
  blurry.

  See screenshots. One shows blurry clock that I switched to, and then
  the non-blurry real clock a few seconds later.

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

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

[Michael Zanetti]

** 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 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 1379757] Re: [phone-app] Could not return out of the dialer-app

[Michael Zanetti]

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

This is a problem of the display driver for the Nexus 4.

** This bug has been marked a duplicate of bug 1408263
   Edge gestures still get lost (mako)

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

Title:
  [phone-app] Could not return out of the dialer-app

Status in Ubuntu UX bugs:
  Fix Released
Status in unity8 package in Ubuntu:
  New

Bug description:
  All ok from begin of using ubuntu on my phone till now. After geted a call, I 
could not return to my apps. If I swiped from left to right, nothing happened.
  Lock my phone and turn it "on" (go in welcome-screen): No I only could swipe 
the welcome away, but could not open the dash at the left site.

  I dont know, if this is a problem of dialer-app or something of the
  system, but it happens in the dialer-app. (It was the first time now.)

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

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

[Touch-packages] [Bug 1438036] Re: Unable to acknowledge alarm

[Michael Zanetti]

Hi Jussi, sorry for the lack of activity in this bug report. We have
fixed some crashers in the notification system (which is used for
showing the alarm) and are confident that this will be fixed with OTA-4.
If it happens again, please reopen the bug report.

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

Title:
  Unable to acknowledge alarm

Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Happened this morning with Bq Aquarius (software version 20). The
  alarm went off, but it was impossible to acknowledge it as the view
  didn't respond to anything. I had to reboot the device.

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

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

[Touch-packages] [Bug 1461682] Re: [MX4] LED does not notify for incoming notifications

[Michael Zanetti]

Yes, works on krillin, doesn't work on arale.

Unity8 uses the android-headers package to accomplish that for krillin.
That gives us the following options to initialize lights:

LIGHT_ID_BACKLIGHT  
LIGHT_ID_KEYBOARD   
LIGHT_ID_BUTTONS
LIGHT_ID_BATTERY
LIGHT_ID_NOTIFICATIONS  
LIGHT_ID_ATTENTION  

Krillin works fine with LIGHT_ID_NOTIFICATIONS, however, arale doesn't.
I have tried with all the others and the only one that actually does
something on arale is LIGHT_ID_BACKLIGHT, which is obviously not what we
want. If we can talk to the lights at all, this probably needs to be
fixed on the android side of things.

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

Title:
  [MX4] LED does not notify for incoming notifications

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

Bug description:
  Image r12

  The notification LED on the device does not blink when a new SMS
  arrives. Its always static off. It however does lighten up when the
  button physical button is pressed.

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

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

[Touch-packages] [Bug 1461729] [NEW] calling pageStack.pop() in a loop pops too much

[Michael Zanetti]

Public bug reported:

In Ubuntu.Components 1.1 this was working fine to pop everything from a
PageStack except the first page:

while (pageStack.depth > 1) {
  pageStack.pop()
}


In Ubuntu.Components 1.2 this does no longer work, because it pops the first 
page too. My suspicion is that it is related to the animation in the header 
which updates the depth asynchronously.

See the attached file as a standalone example to reproduce. While it
works when importing 1.1, it breaks when importing 1.2

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

** Attachment added: "pageStack.qml"
   
https://bugs.launchpad.net/bugs/1461729/+attachment/4409484/+files/pageStack.qml

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

Title:
  calling pageStack.pop() in a loop pops too much

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

Bug description:
  In Ubuntu.Components 1.1 this was working fine to pop everything from
  a PageStack except the first page:

  while (pageStack.depth > 1) {
pageStack.pop()
  }

  
  In Ubuntu.Components 1.2 this does no longer work, because it pops the first 
page too. My suspicion is that it is related to the animation in the header 
which updates the depth asynchronously.

  See the attached file as a standalone example to reproduce. While it
  works when importing 1.1, it breaks when importing 1.2

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

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

[Touch-packages] [Bug 1249333] Re: UbuntuWebView doesn't regard GRID_UNIT_PX

[Michael Zanetti]

Hi Olivier,

Here's a screenshot using a test app with Ubuntu.Web 0.2:

http://i.imgur.com/E6Hzq8s.png

On the left, started with GRID_UNIT_PX=8, on the right with
GRID_UNIT_PX=16

So looks to me as this is still valid.

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

Title:
  UbuntuWebView doesn't regard GRID_UNIT_PX

Status in Web Browser App:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  On High-DPI screens like the Apple Retina Display all Ubuntu
  Components and apps adjust nicely to the DPI by setting the
  GRID_UNIT_PX env variable. One exception to this is the UbuntuWebView
  which loads websites very, very tiny on such displays, regardless of
  the used GRID_UNIT_PX value.

  The WebView has it's own env variable, QTWEBKIT_DPR, which allows
  adjusting it's resolution. However, this isn't obvious to users and
  especially on desktop systems QTWEBKIT_DPR is mostly not set to
  anything.

  Couldn't we initialize QTWEBKIT_DPR to a sane value calculated from
  the GRID_UNIT_PX value in case it is not explicitly set?

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

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

[Touch-packages] [Bug 1463370] Re: Keyboard autorepeat missing

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

** 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/1463370

Title:
  Keyboard autorepeat missing

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using Unity8 (8.02+15.04.20150409.1-0ubuntu1) on a desktop from this
  image http://cdimage.ubuntu.com/ubuntu-desktop-next/backup-20150422/

  Apps (terminal, messaging and others) have no keyboard auto-repeat.
  This makes keyboard navigation and backspace slow and cumbersome.

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

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

[Touch-packages] [Bug 1464367] Re: NetworkingStatus.online is always false on desktop

[Michael Zanetti]

Meh... it's NetworkingStatus.Online (uppercase). Sorry for the noise.

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

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

Title:
  NetworkingStatus.online is always false on desktop

Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  As the summary says, even though I'm online with my notebook,
  NetworkingStatus.online always returns false.

  I haven't used it much lately, but when I was using it last, about a
  month ago it was still working.

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

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

[Touch-packages] [Bug 1464367] [NEW] NetworkingStatus.online is always false on desktop

[Michael Zanetti]

Public bug reported:

As the summary says, even though I'm online with my notebook,
NetworkingStatus.online always returns false.

I haven't used it much lately, but when I was using it last, about a
month ago it was still working.

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

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

Title:
  NetworkingStatus.online is always false on desktop

Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  As the summary says, even though I'm online with my notebook,
  NetworkingStatus.online always returns false.

  I haven't used it much lately, but when I was using it last, about a
  month ago it was still working.

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

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

[Touch-packages] [Bug 1464390] [NEW] Feature request: allow invoking a websearch using the configured search engine

[Michael Zanetti]

Public bug reported:

Some apps may want to trigger a web search in the browser. Right now
there is the possibility to do something like

Qt.openUrlExternally("https://google.com?q=foobar";)

However, the search engine might be blocked in some countries or not be
the user's favourite one. It would be great if we could do something
like:

Qt.openUrlExternally("websearch://foobar")

I haven't fully thought the websearch:// scheme through yet, so probably
this requires a case study on the used uri scheme and/or query
arguments. Maybe there's some standard uri scheme for this? Or maybe
even just something like http://foobar?

** Affects: tagger
 Importance: Medium
 Assignee: Michael Zanetti (mzanetti)
 Status: Confirmed

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

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

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

Title:
  Feature request: allow invoking a websearch using the configured
  search engine

Status in Tagger:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Some apps may want to trigger a web search in the browser. Right now
  there is the possibility to do something like

  Qt.openUrlExternally("https://google.com?q=foobar";)

  However, the search engine might be blocked in some countries or not
  be the user's favourite one. It would be great if we could do
  something like:

  Qt.openUrlExternally("websearch://foobar")

  I haven't fully thought the websearch:// scheme through yet, so
  probably this requires a case study on the used uri scheme and/or
  query arguments. Maybe there's some standard uri scheme for this? Or
  maybe even just something like http://foobar?

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

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

[Touch-packages] [Bug 1464390] Re: Feature request: allow invoking a websearch using the configured search engine

[Michael Zanetti]

Adding Tagger as that one has a hardcoded search engine and thus fails
to search in some countries.

** Changed in: tagger
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

** Changed in: tagger
   Status: New => Confirmed

** Changed in: tagger
   Importance: Undecided => Medium

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

Title:
  Feature request: allow invoking a websearch using the configured
  search engine

Status in Tagger:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Some apps may want to trigger a web search in the browser. Right now
  there is the possibility to do something like

  Qt.openUrlExternally("https://google.com?q=foobar";)

  However, the search engine might be blocked in some countries or not
  be the user's favourite one. It would be great if we could do
  something like:

  Qt.openUrlExternally("websearch://foobar")

  I haven't fully thought the websearch:// scheme through yet, so
  probably this requires a case study on the used uri scheme and/or
  query arguments. Maybe there's some standard uri scheme for this? Or
  maybe even just something like http://foobar?

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

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

[Touch-packages] [Bug 1465051] Re: Lock screen does not react on input/swipes

[Michael Zanetti]

Once the device is unlocked, do the edges work again? I.e. Can you
switch apps using the right edge or pull in the launcher?

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

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

Title:
  Lock screen does not react on input/swipes

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Can't get to unlock: when I try to swipe away lock screen nothing
  happens.

  Can get beyond the screen using active icons in the notification area,
  e.g. if I select battery indicator and then options, input secret code
  screen gets activated and I can access the device.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.02+15.04.20150406~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Sun Jun 14 21:42:48 2015
  InstallationDate: Installed on 2015-05-08 (37 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150508-031218)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1465051] Re: Lock screen does not react on input/swipes

[Michael Zanetti]

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

Alexey, thanks for the report.

In that case this is a duplicate of bug #1391149 and will be fixed with
OTA-4.


** This bug has been marked a duplicate of bug 1391149
   greeter not reacting to swipes

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

Title:
  Lock screen does not react on input/swipes

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Can't get to unlock: when I try to swipe away lock screen nothing
  happens.

  Can get beyond the screen using active icons in the notification area,
  e.g. if I select battery indicator and then options, input secret code
  screen gets activated and I can access the device.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.02+15.04.20150406~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Sun Jun 14 21:42:48 2015
  InstallationDate: Installed on 2015-05-08 (37 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150508-031218)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1461682] Re: [MX4] LED does not notify for incoming notifications

[Michael Zanetti]

According to ogra we can control the light using: /sys/class/leds/mx-
led/trigger

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

Title:
  [MX4] LED does not notify for incoming notifications

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

Bug description:
  Image r12

  The notification LED on the device does not blink when a new SMS
  arrives. Its always static off. It however does lighten up when the
  button physical button is pressed.

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

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

[Touch-packages] [Bug 1378267] Re: Suspended app screenshots are blurry

[Michael Zanetti]

So the problem is this:

When an app gets killed by a low memory condition, only a screenshot is
kept in the right edge spred. If the user then clicks on that
screenshot, it is animated to foreground and the app restarted behind
the scenes. However, starting an app might take a bit. During this time,
the screenshot appears frozen to the user. While presenting a blurred
screenshot is not good, I think just adding a full-resolution screenshot
isn't good either because the user will try to interact with it.

So we'd need a design on what to do with the screenshot (probably
desaturated or something) and if there should be a spinner or something
on top of it to indicate that it's loading.

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

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

Title:
  Suspended app screenshots are blurry

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

Bug description:
  It's really obvious that an app has been suspended when I switch to it
  and the screengrab is really blurry. Would be really nice if it wasn't
  blurry.

  See screenshots. One shows blurry clock that I switched to, and then
  the non-blurry real clock a few seconds later.

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

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

[Touch-packages] [Bug 1465539] Re: Is it OK to change the app layout to vertical?

[Michael Zanetti]

Well, if you get an SMS you can see the content of it in the
notification area accessible from the top edge. Also showing the apps
spread horizontally doesn't really show you more content of the app,
just a different portion of it.

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

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

Title:
  Is it OK to change the app layout to vertical?

Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  I just upgraded my Android phone to 5.0. Attached please the captured
  picture. The running apps on android are displayed in a vertical
  structure, which seems to me more reasonable since I can see some of
  the content of the apps without opening them. For example, if an SMS
  comes to the phone with a code which is needed for authentication on
  payment, I do not need to open the app and I can know the content of
  the SMS, then I can switch back to my app to input the code.

  Currently, our design shows all of the app in the horizontal way. A
  user has no way to view some part of the content without opening it.
  Also, it is good to have "X" as shown in the android app though
  swiping is a way to kill the app.

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

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

[Touch-packages] [Bug 1465541] Re: rotate phone to 90 degrees, front camera not show full screen viewfinder

[Michael Zanetti]

** Package changed: unity8 (Ubuntu) => camera-app

** Changed in: camera-app
   Importance: Undecided => Critical

** Changed in: camera-app
   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/1465541

Title:
  rotate phone to 90 degrees,front camera not show full screen
  viewfinder

Status in Camera App:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 25
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-06-16 10:43:25
  version version: 25
  version ubuntu: 20150615.1
  version device: 20150608-6e66f3c
  version custom: 20150602-731-5-32

  steps:
  1.launch camera app then switch to front camera
  2.rotate phone to 90 degrees

  expect result:
  the front camera  show a full screen viewfinder

  actual result:
  the front camera show partial screen viewfinder

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

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

[Touch-packages] [Bug 1465961] Re: Ubuntu shape sometimes becomes pixelated in OTA-4

[Michael Zanetti]

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

** This bug has been marked a duplicate of bug 1455567
   [UbuntuShape] Broken rendering under certain device orientation conditions

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

Title:
  Ubuntu shape sometimes becomes pixelated in OTA-4

Status in unity8 package in Ubuntu:
  New

Bug description:
  Hi, I have noticed a refinement in Ubuntu shape icons in launcher and
  menus in OTA-4, since they now look smoother than before.

  However, about 5 or 6 times a day, since I installed the OTA-4 I have
  also noticed that sometimes when you make the launcher appear or
  unlock the phone, the shape of the icons (launcher and scopes) appears
  very pixelated (I attach a pic to illustrate that). It get solved just
  by hiding the launcher and showing it again, and the icons are again
  correctly shaped. Can you please fix this?

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

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

[Touch-packages] [Bug 1455107] Re: Creating and destroying SoundEffects causes crashes

[Michael Zanetti]

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

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

Title:
  Creating and destroying SoundEffects causes crashes

Status in the base for Ubuntu mobile products:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in qtmultimedia-opensource-src package in Ubuntu:
  New

Bug description:
  I keep on receiving bug reports about Machines vs. Machines being
  crashy on Ubuntu Phones and I tracked it down to the SoundEffect item.
  When playing without sound effects enabled, the game seems very
  stable.

  To get to the bottom of this I created an app that simulates a bit how
  a game works with sound effects. It's a bit more aggressive than
  Machines-vs-Machines (still not really far fetched from a real game
  scenario) and reliably triggers some crashers in less than a minute
  here.

  So far I've seen crashes in creating SoundEffects items as well as
  removing them from the scene.

  Please find the example here: lp:~mzanetti/+junk/soundcrasher

  You should be able to run it on any vivid powered device by just
  opening the .pro file in QtCreator and hit the play button. The logs
  vary a lot between crashes. Sometimes I get some PulseAudio messages,
  sometimes it just crashes without any. Probably some raciness. Anyhow,
  this example app should give the system a hard time and reveal most of
  the crashes eventually.

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

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

[Touch-packages] [Bug 1465858] Re: Time can not be read when alarm is set (while swiping/opening indicator)

[Michael Zanetti]

** Package changed: unity8 (Ubuntu) => indicator-datetime (Ubuntu)

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

Title:
  Time can not be read when alarm is set (while swiping/opening
  indicator)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I am on krillin r23 stable (OTA-4), but I have reproduced this bug on
  mako (stable channel) too.

  0. launch a full screen app like Machine Vs Machines. NO alarm set.
  1. can't see the time (expected) because when in full screen: top bar 
indicator is hidden
  2. swipe from top edge and focus time indicator: you can read the time at the 
top of the time label indicator (expected)

  Now

  0. launch a full screen app like Machine Vs Machines. At least 1 alarm is set 
and due in the futur.
  1. can't see the time (expected) because when in full screen : top bar 
indicator is hidden
  2. swipe from top edge and focus time indicator: you can't read the time at 
the top of the time label's indicator because the time is replaced by the alarm 
icon (not expected)

  Current UX to see the time (alternative solution until it get fixed):

  3. swipe from left side, and focus another app not in full screen (or go 
scope with left swipe)
  4. see time from top bar indicators.
  5. swipe from right to get back at your focused apps.

  Or :
  3. push power (screen off)
  4. push power (screen on, lock screen)
  5. check the time at the top bar indicator
  6. unlock to get back to yout focused app.

  5 or 6  steps are needed to just watch the time while only 1or2 could
  do the work if the time was always shown on the indicator time's icon.

  I beleive this is not a niche need :
   * Alarms are usual
   * Full screen apps too
   * checking time too

  PS: please affect the bug to indicator if needed, It fails when I
  tryed submit from here https://bugs.launchpad.net/ubuntu/+source
  /indicator-time/+filebug

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

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

[Touch-packages] [Bug 1497145] [NEW] UbuntuShape is missing type information

[Michael Zanetti]

Public bug reported:

In the UbuntuSDK, the UbuntuShape does not support autocompletion, will
not be recognized by the Syntax highlighter and code completion does not
work for its properties. In short, it's missing all type information for
the IDE.

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

** Description changed:

  In the UbuntuSDK, the UbuntuShape does not support autocompletion, will
  not be recognized by the Syntax highlighter and code completion does not
- work for it's property. In short, it's missing all type information for
+ work for its properties. In short, it's missing all type information for
  the IDE.

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

Title:
  UbuntuShape is missing type information

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

Bug description:
  In the UbuntuSDK, the UbuntuShape does not support autocompletion,
  will not be recognized by the Syntax highlighter and code completion
  does not work for its properties. In short, it's missing all type
  information for the IDE.

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

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

[Touch-packages] [Bug 1497095] Re: Two identical grey window buttons for minimize and maximize

[Michael Zanetti]

Still haven't received assets from design...

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

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

Title:
  Two identical grey window buttons for minimize and maximize

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

Bug description:
  Two identical grey window buttons for minimize and maximize. Which is
  which? Click them and find out :)

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

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

[Touch-packages] [Bug 1497097] Re: [enhancement] Add non-linear animation progress (e.g. fast and then decelerating) for minimize/maximize

[Michael Zanetti]

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

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

Title:
  [enhancement] Add non-linear animation progress (e.g. fast and then
  decelerating) for minimize/maximize

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

Bug description:
  [enhancement] Add non-linear animation progress (e.g. fast and then
  decelerating).

  The current linear animations for minimize/maximize look kind of
  awkward and unnatural.

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

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