[Touch-packages] [Bug 1613613] Re: sometimes header of the dialler is clipped on incoming calls

[Selene Scriven]

Appears to be fixed in silo 67.

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

Title:
  sometimes header of the dialler is clipped on incoming calls

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

Bug description:
  current build number: 402
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Sometimes when receiving a call the dialler is not fully visible and
  the header is clipped, like the entire page is slightly scrolled (cf
  screenshot)

  Test Case:
  1. On the DUT, close the dialler app and lock the phone
  2. Call the DUT from another phone
  3. Take the call and wait until the dialler UI is fully rendered.

  Expected result
  The whole UI is visible

  Actual result
  The header is clipped.

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

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

[Touch-packages] [Bug 1613613] Re: sometimes header of the dialler is clipped on incoming calls

[Selene Scriven]

I see this consistently on krillin and arale.  Well, 3 out of 3 tries
anyway.  Has anyone bisected it yet?

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

Title:
  sometimes header of the dialler is clipped on incoming calls

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

Bug description:
  current build number: 402
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Sometimes when receiving a call the dialler is not fully visible and
  the header is clipped, like the entire page is slightly scrolled (cf
  screenshot)

  Test Case:
  1. On the DUT, close the dialler app and lock the phone
  2. Call the DUT from another phone
  3. Take the call and wait until the dialler UI is fully rendered.

  Expected result
  The whole UI is visible

  Actual result
  The header is clipped.

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

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

[Touch-packages] [Bug 1607799] Re: Dash freezes after U1 login

[Selene Scriven]

As far as I can tell, this is when the bug started:
https://requests.ci-train.ubuntu.com/#/ticket/1582
https://code.launchpad.net/~mardy/libsignon-glib/unregistered-lp1593805/+merge/298096

I ran into the issue today and tracked it down to that specific image
(and that landing seems the most likely candidate), which led me to this
bug.

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

Title:
  Dash freezes after U1 login

Status in Canonical System Image:
  In Progress
Status in libsignon-glib package in Ubuntu:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity-scopes-shell package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Without U1 account, go to Ubuntu Store.
  - Tap on an app.
  - Tap on the install button.
  - Introduce credentials.

  Expected result.
  - After credentials, the app is installed.

  Actual result.
  - Dash is frozen. Cannot go back to the scopes. Launcher and indicators do 
work, though. There is no crash.

  current build number: 389
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

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

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

[Touch-packages] [Bug 1565941] Re: Dual Panel view: Updating an image on a contact changes on details panel but not in the contact list

[Selene Scriven]

Seems fixed in silo 46.

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

Title:
  Dual Panel view: Updating an image on a contact changes on details
  panel but not in the contact list

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  Pre-Requisite: have some images in the gallery app
  1. Open addressbook On a tablet in dual panel mode
  2. Create a new contact
  3. Add an image from gallery
  4. Hit save
  5. Close the app
  6. Open the app
  7. Hit edit
  8. Tap on the image 
  9. Select camera and take a photo
  10. Add that image to the contact
  11. save the contact edits

  EXPECTED:
  I expect the image in the contacts list to match the image in on the edit page

  ACTUAL:
  The image in the contact list panel is different to the image in the details 
panel see attached screenshot

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

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

[Touch-packages] [Bug 1583014] Re: can't import contacts from google from messaging-app when no contacts exist

[Selene Scriven]

Seems to be fixed in silo 46.

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

Title:
  can't import contacts from google from messaging-app when no contacts
  exist

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed
Status in online-accounts-api package in Ubuntu:
  New

Bug description:
  Trying to send an sms, I click on the "person" icon to choose a
  contact. I have none, and the options are "+ Create new", "Import
  contacts from Google" and " Import contacts from SIM card". If I click
  the google option it does nothing (shows loading and goes back to the
  same screen showing the options) I guess it should take me to the "add
  google account" config somehow instead?

  Original reporter: Julia Palandri

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

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

[Touch-packages] [Bug 1592422] Re: Contact's field labels don't show up

[Selene Scriven]

Seems fixed in silo 46.

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

Title:
  Contact's field labels don't show up

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  In Progress

Bug description:
  Test case.
  - Open messaging app.
  - Swipe up to create a new message.
  - Tap on the Contact icon.
  - Tap to Create a new contact.

  Expected result.
  - Contact's field labels can be read ("Name", "Last name").

  Actual result.
  - Contact's field labels cannot be read (probably have the same color as 
background).

  In OTA11 they can be read.

  current build number: 350
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

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

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

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

[Selene Scriven]

Subscribing so I can get notified to power-test the changes when they're
available.

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1488959] Re: Tapping screen when dimmed should just restore the brightness and not activate a component

[Selene Scriven]

Hi, if this had a fix committed way back in September, is there a reason
why it's still not released?  For now, I'm assuming the spec was updated
but no code has been written?

Today's build still activates whatever the user tapped, instead of just
bumping the brightness back up and resetting the dimming timer.

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

Title:
  Tapping screen when dimmed should just restore the brightness and not
  activate a component

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

Bug description:
  When the screen dims a tap to restore brightness is also processed by
  the underlying component. This is consistent with Android but not how
  iOS behaves which is preferred by several users.

  -- UX comment --

  As the bug description suggests, a tap on the dimmed screen should
  simply wake up the phone into the full lit state. This means no action
  should be triggered.

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

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

[Touch-packages] [Bug 1579837] Re: Issue after wizard with policykit

[Selene Scriven]

This is interesting.  I've been having to override the auth type after
the wizard for years, since it always gives me passphrase even if I
select pin and enter a 4-digit code.  Didn't realize there was a new
issue with the same symptoms.

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

Title:
  Issue after wizard with policykit

Status in Canonical System Image:
  In Progress
Status in accountsservice package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Bootstrap flash a fresh image to a device
  2. Run through the wizard selecting pin for authentication
  3. Tap on the get started button
  4. Phone freezes for a while
  5. At some point it unfreezes and you see the dash
  6. Reboot and get password login instead of pin login

  EXPECTED:
  I expect no freeze (possibly due to apport) and pin dialogue on reboot

  ACTUAL:
  I get a long freeze and on reboot instead of getting the pin dialogue to 
unlock the phone I get the password dialogue and full osk.

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

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

[Touch-packages] [Bug 1434576] Re: Quick scroll in contacts sometimes doesn't scroll the content

[Selene Scriven]

With silo 036 / ticket 1371 installed, I still see something which looks
like this bug.

First I import contacts to fill up the address book with several pages
of names.  Then if I swipe to start a fast scroll downward, and tap
lightly on an early letter like A or B or C, it will sometimes not work
correctly.  Instead of jumping to the selected letter and stopping, what
I see is the letter index highlight moves briefly to what I touched,
then goes back down and the page continues scrolling as if I hadn't
touched anything.

The only indication that I touched the screen is that the highlight
moves to the letter I touched for a fraction of a second.

If I hold the selected letter longer, it seems to function as expected.
So, it looks like the bug requires a very quick tap.

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

Title:
  Quick scroll in contacts sometimes doesn't scroll the content

Status in Canonical System Image:
  In Progress
Status in address-book-app package in Ubuntu:
  In Progress

Bug description:
  Mako running rtm 214

  Open contacts
  scroll up to reveal the quick scroll letter set
  tap on a letter
  sometimes the list scrolls to the letter and sometimes it does not move
  It seems to do this when the contents are still moving when the tap is done 
but its not 100%

  see attached video

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

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

[Touch-packages] [Bug 1579915] Re: network-manager 1.2 uses more power

[Selene Scriven]

To clarify, the failed case was the last good image plus updates to
network-manager and libnm0.  Nothing else was upgraded.

The unchanged case updated nearly everything else.  Here's apt's full
description:

The following packages have been kept back:
  libsystemsettings1 network-manager ubuntu-system-settings ubuntu-touch
The following packages will be upgraded:
  account-polld cameraplugin-aal dialer-app gir1.2-ubuntu-app-launch-2
  history-service indicator-datetime indicator-display indicator-network
  indicator-sound isc-dhcp-client isc-dhcp-common language-pack-touch-ast
  language-pack-touch-bg language-pack-touch-bs language-pack-touch-ca
  language-pack-touch-cs language-pack-touch-da language-pack-touch-de
  language-pack-touch-el language-pack-touch-en language-pack-touch-es
  language-pack-touch-eu language-pack-touch-fi language-pack-touch-fr
  language-pack-touch-gd language-pack-touch-gl language-pack-touch-he
  language-pack-touch-hr language-pack-touch-hu language-pack-touch-id
  language-pack-touch-it language-pack-touch-ja language-pack-touch-ko
  language-pack-touch-lt language-pack-touch-lv language-pack-touch-ms
  language-pack-touch-nb language-pack-touch-nl language-pack-touch-oc
  language-pack-touch-pa language-pack-touch-pl language-pack-touch-pt
  language-pack-touch-ro language-pack-touch-ru language-pack-touch-sk
  language-pack-touch-sl language-pack-touch-sr language-pack-touch-sv
  language-pack-touch-tr language-pack-touch-ug language-pack-touch-uk
  language-pack-touch-zh-hans language-pack-touch-zh-hant
  libandroid-properties1 libconnectivity-qt1 libhardware2 libhistoryservice0
  libhybris libhybris-common1 libhybris-test libhybris-utils liblibertine1
  libmedia-hub-client4 libmedia-hub-common4 libmedia1 libnm-glib-vpn1
  libnm-glib4 libnm-util2 libonline-accounts-client1 libqt5qml5 libqt5quick5
  libqt5quickparticles5 libqt5quicktest5 libubuntu-app-launch2
  libubuntugestures5 libubuntutoolkit5 libunity-api0 lxc-android-config
  media-hub mediaplayer-app messaging-app qml-module-qt-labs-folderlistmodel
  qml-module-qt-labs-settings qml-module-qtqml-models2
  qml-module-qtqml-statemachine qml-module-qtquick-localstorage
  qml-module-qtquick-particles2 qml-module-qtquick-window2
  qml-module-qtquick-xmllistmodel qml-module-qtquick2 qml-module-qttest
  qml-module-ubuntu-components qml-module-ubuntu-connectivity
  qml-module-ubuntu-layouts qml-module-ubuntu-onlineaccounts-client
  qml-module-ubuntu-performancemetrics qml-module-ubuntu-test
  qml-module-ubuntu-ui-extras-browser qml-module-ubuntu-web qmlscene
  qtdeclarative5-folderlistmodel-plugin qtdeclarative5-localstorage-plugin
  qtdeclarative5-online-accounts-client0.1 qtdeclarative5-particles-plugin
  qtdeclarative5-qtmir-plugin qtdeclarative5-qtquick2-plugin
  qtdeclarative5-ubuntu-history0.1
  qtdeclarative5-ubuntu-keyboard-extensions0.1
  qtdeclarative5-ubuntu-settings-components
  qtdeclarative5-ubuntu-telephony-phonenumber0.1
  qtdeclarative5-ubuntu-telephony0.1
  qtdeclarative5-ubuntu-ui-extras-browser-plugin
  qtdeclarative5-ubuntu-ui-extras0.2 qtdeclarative5-ubuntu-ui-toolkit-plugin
  qtdeclarative5-ubuntu-web-plugin qtdeclarative5-window-plugin
  qtdeclarative5-xmllistmodel-plugin qtmir-android qtubuntu-android
  qtubuntu-media suru-icon-theme telephony-service ubuntu-app-launch
  ubuntu-app-launch-tools ubuntu-keyboard ubuntu-keyboard-arabic
  ubuntu-keyboard-azerbaijani ubuntu-keyboard-bosnian ubuntu-keyboard-catalan
  ubuntu-keyboard-chinese-pinyin ubuntu-keyboard-croatian
  ubuntu-keyboard-czech ubuntu-keyboard-danish ubuntu-keyboard-data
  ubuntu-keyboard-dutch ubuntu-keyboard-emoji ubuntu-keyboard-english
  ubuntu-keyboard-finnish ubuntu-keyboard-french ubuntu-keyboard-german
  ubuntu-keyboard-greek ubuntu-keyboard-hebrew ubuntu-keyboard-hungarian
  ubuntu-keyboard-icelandic ubuntu-keyboard-italian ubuntu-keyboard-japanese
  ubuntu-keyboard-norwegian-bokmal ubuntu-keyboard-polish
  ubuntu-keyboard-portuguese ubuntu-keyboard-romanian ubuntu-keyboard-russian
  ubuntu-keyboard-scottish-gaelic ubuntu-keyboard-serbian
  ubuntu-keyboard-slovenian ubuntu-keyboard-spanish ubuntu-keyboard-swedish
  ubuntu-keyboard-ukrainian ubuntu-mobile-icons ubuntu-mono ubuntu-push-client
  ubuntu-sdk-libs ubuntu-system-settings-online-accounts
  ubuntu-ui-toolkit-theme unity-plugin-scopes unity-system-compositor
  unity-webapps-qml unity8 unity8-common unity8-private webapp-container
  webbrowser-app wpasupplicant xmir xserver-common
174 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 72.9 MB of archives.
After this operation, 385 kB of additional disk space will be used.

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

Title:
  network-manager 1.2 uses more power

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

Bug 

[Touch-packages] [Bug 1579915] Re: network-manager 1.2 uses more power

[Selene Scriven]

** Summary changed:

- big power increase in May 4th and later builds
+ network-manager 1.2 uses more power

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

Title:
  network-manager 1.2 uses more power

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

Bug description:
  On krillin and arale, power use went up significantly in new builds starting 
on May 4.  So far, I have results for:
  * krillin rc-proposed 324 and 325
  * arale rc-proposed 316 and 317

  When the radios are off, results are unchanged.  However, power went up in 
two common cases -- standby with all radios enabled, and screen-on with radios 
enabled.
  * krillin standby: ~8mA -> ~80mA
  * arale standby: ~35mA -> ~79mA
  * krillin screen-on: ~177mA -> ~215mA
  * arale screen-on: ~305mA -> ~353mA

  Quite a few things landed in that build, but some of the top suspects are:
  * network-manager got updated to 1.2
  * indicator-network got a cell data switch
  * USS got "fixes to sleep/idle settings"
  * ubuntu-push got a fix related to network-manager
  * libhybris got partial support for wireless display
  * account-polld got a new calendar plugin

  Full list:
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog

  This change cuts typical standby time anywhere from 50% to 90%, so it
  probably should be fixed before release.  However, tests suggest that
  simply turning off wifi returns the phone to a nice low standby power
  -- about 6mA for both devices.

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

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

[Touch-packages] [Bug 1558531] Re: Set up VPN page breaks navigation pattern

[Selene Scriven]

I personally don't care which style is used, but at the moment it's
still not consistent.  Here are the VPN and APN config screens.

** Attachment added: "vpn-apn-ui.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1558531/+attachment/4656648/+files/vpn-apn-ui.png

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

Title:
  Set up VPN page breaks navigation pattern

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  Every page that I have come across in Ubuntu Touch apps, use a back
  header button to exit the page. The "Set up VPN" places the "Cancel"
  and "Ok" buttons at the bottom of the page which makes it confusing
  and undiscoverable for a user. To compound the issue, if the user
  panics and just closes the system settings app at that point, a VPN
  connection is still created (bug 1558530).

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

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

[Touch-packages] [Bug 1558531] Re: Set up VPN page breaks navigation pattern

[Selene Scriven]

I tested the fix and it does not appear to make the UI any more
consistent compared to the rest of the system-settings app.

For example, look at the UI to add a new APN.  Instead of "cancel" and
"ok" at the bottom, it has a back button and a checkmark in the header.

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

Title:
  Set up VPN page breaks navigation pattern

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  Every page that I have come across in Ubuntu Touch apps, use a back
  header button to exit the page. The "Set up VPN" places the "Cancel"
  and "Ok" buttons at the bottom of the page which makes it confusing
  and undiscoverable for a user. To compound the issue, if the user
  panics and just closes the system settings app at that point, a VPN
  connection is still created (bug 1558530).

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

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

[Touch-packages] [Bug 1570616] Re: gallery app is not stripped

[Selene Scriven]

Appears to be fixed in gallery-app 2.9.1.1312.

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

Title:
  gallery app is not stripped

Status in Canonical System Image:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  The gallery app binary should be stripped to reduce file size and disk
  footprint

  find com.ubuntu.gallery/ -type f | xargs file | grep 'not stripped'
  com.ubuntu.gallery/2.9.1.1292/gallery-app:
   ELF 32-bit LSB executable, ARM, EABI5 version 1 
(GNU/Linux), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for 
GNU/Linux 2.6.32, BuildID[sha1]=9de0e3960f947e44d20999aeed3161fd9c5d5ba6, not 
stripped

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

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

[Touch-packages] [Bug 1569844] Re: gallery does not update images when invoked by content hub

[Selene Scriven]

Appears to be fixed in gallery-app 2.9.1.1312.

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

Title:
  gallery does not update images when invoked by content hub

Status in Canonical System Image:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  * Make sure the gallery app is closed
  * Open the camera app, take a picture (or press vol+/- to take a screenshot)
  * Open the telegram app, open a conversation
  * click on "attach image"
  * in the ContentPeerPicker, select the gallery app

  => Gallery app will open, but your new picture is not around.

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

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

[Touch-packages] [Bug 1536168] Re: gallery app shows non-image formats (tgz)

[Selene Scriven]

Appears to be fixed in gallery-app 2.9.1.1312.

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

Title:
  gallery app shows non-image formats (tgz)

Status in Canonical System Image:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  current build number: 41
  device name: krillin
  channel: ubuntu-touch/rc/bq-aquaris.en

  Test Case:
  1. Create a tgz file in the Pictures directory
  $ tar czf ~/Pictures/test.tgz ~/Pictures/com.ubuntu.camera/
  2. Open the gallery app

  Actual Result:
  The gallery app shows a blank preview corresponding to the tgz, if you tap on 
it, there is a black screen and the spinner keeps spinning.
  If there is an SD Card, the gallery tries to read tgz from it even if they 
are not in a Pictures directory:
  
file:///usr/share/click/preinstalled/com.ubuntu.gallery/2.9.1.1260/rc/qml/MediaViewer/SingleMediaViewer.qml:157:17:
 QML Image: Failed to get image from provider: 
image://photo/file:///media/phablet/Médias SDc/backup/phablet.20150702.tgz

  
  Expected Result
  the tgz is not visible in the gallery

  mediascanner correctly identifies the file as not being a video or audio file 
  New file was created: /home/phablet/Pictures/test.tgz.
  Error when adding new file: File /home/phablet/Pictures/test.tgz is not audio 
or video

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

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

[Touch-packages] [Bug 1560159] Re: Gallery does not launch on the last opened view

[Selene Scriven]

Gallery-app 2.9.1.1312 appears to fix this.

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

Title:
  Gallery does not launch on the last opened view

Status in Canonical System Image:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  Tested on krillin with rc-proposed (r286):

  Steps:
  1. Open gallery-app
  2. Move to Photos view
  3. Close gallery-app
  4. Re-open gallery-app

  Expected result:
  gallery-app launches showing the last opened view, Photos view in this case.

  Current result:
  gallery-app launches showing Events view

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

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

[Touch-packages] [Bug 1568310] Re: BQ E4.5 (OTA-10): gallery-app tries to index thousands of files on the SD card, but should not

[Selene Scriven]

Gallery-app 2.9.1.1312 partially fixes this.  It doesn't index new files
under a .nomedia marker, but if the .nomedia marker is added after
indexing, gallery-app continues to show those files.  So, at the moment
it is necessary to remove the gallery index database in order to make it
stop showing .nomedia-excluded images.

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

Title:
  BQ E4.5 (OTA-10): gallery-app tries to index thousands of files on the
  SD card, but should not

Status in Canonical System Image:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:

  The app gallery did not started anymore in my BQ E4.5, it was just
  sitting there and loading  for hours without coming to an end. I 
investigated
  it with strace and lsof and saw the app was searching through all the
  100.000 files (OSM tiles) on my SD card. While the SD card managment app
  supports placing a file there with the name '.nomedia' so the SD Card
  app ignores all files and dirs below:

  $ ls -la /media/phablet/4BDC-71D9/Maps
  total 840900
  drwxr-xr-x  3 phablet phablet  4096 Apr  7 09:25 .
  drwxr-xr-x  8 phablet phablet  4096 Jan  1  1970 ..
  -rw-r--r--  1 phablet phablet 0 Apr  4 14:58 .nomedia
  drwxr-xr-x 19 phablet phablet  4096 Apr  4 14:08 osm

  $ find /media/phablet/4BDC-71D9/Maps/osm | wc -l
  129236

  it seems that the gallery-app does not honor this file '.nomedia'.

  Any idea for a workaround in the gallery-app?

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

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

[Touch-packages] [Bug 1577035] Re: [M10 tablet] Dekko can not scroll up when replying in desktop mode

[Selene Scriven]

On many other systems, this issue was solved by making the OSK appear in
a regular window instead of an overlay, and then tiling the window
layout.  So, it was guaranteed not to overlap anything, and apps didn't
have to do anything special to handle scrolling when the keyboard was
visible, because the window manager resized the windows automatically.
Simple and effective.

On a non-tiling window manager this would be more difficult, like unity8
in desktop mode.  But I've seen this solved in non-tiling window
managers too, by giving some windows an "avoid" property to prevent
overlap with other windows.  If the keyboard goes along an entire edge
of the screen, the WM can mostly pretend the screen is temporarily
smaller, which is pretty simple.  But that doesn't allow making the
keyboard narrower than the screen, so it might be a better idea to do a
more complex version of the "avoid" concept.

Regardless, it's tricky to do partial tiling in a non-tiling window
manager.

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

Title:
  [M10 tablet] Dekko can not scroll up when replying in desktop mode

Status in Dekko:
  Confirmed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  
  This problem is with the M10 Ubuntu tablet. When I have it in the so
  called desktop mode and try to answer an email, the on screen keyboard
  covers nearly the half of the screen high (which IMHO is to much, others do 
not
  agree), but more problematic is, that I can't scroll the buffer of Dekko
  more up to see the cursor and the text while writing, when I put it
  below the last line of the message I'm replying to. See the two attached
  screens.

  And I do not like top posting, i.e. do not come up with this hint :-)

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

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

[Touch-packages] [Bug 1571094] Re: /usr/bin/phone-gsettings-migration.py:ValueError:/usr/bin/phone-gsettings-migration.py@27:__call__:call_blocking

[Selene Scriven]

Was going to report this, but it seems someone else got to it first.  :)

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

Title:
  /usr/bin/phone-gsettings-migration.py:ValueError:/usr/bin/phone-
  gsettings-migration.py@27:__call__:call_blocking

Status in Canonical System Image:
  In Progress
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding telephony-service.  This problem was most recently seen with
  version 0.1+15.04.20160411-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/e33f885bbc5d071b30c62ddbad840cf30b893ef4
  contains more details.

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

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

[Touch-packages] [Bug 1472789] Re: libmtp error copying big files

[Selene Scriven]

I copied a 4.3 GiB file to an arale with this fix, via gmtp, and it
worked well with matching md5sums before and after.  So, it looks like
it's fixed.  :)

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

Title:
  libmtp error copying big files

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

Bug description:
  An error message is shown when trying to copy a file of 3GB from my
  ubuntu desktop to my krillin phone using Nautilus.

  Steps to reproduce:
  1. Plug a krillin device 
  2. Create a file with > dd if=/dev/urandom of=/tmp/bigfile.txt bs=1024 
count=300
  3. Using Nautilus, copy the file to the Documents directory in the device

  In my machine it is happening that after that 2.1 GB are copied the
  process does not copy more content and an error screen appears (see
  atached). The error displayed is: "libmtp error: Could not send
  object"

  
  The free space in my device is about 3.7 GB
  My desktop os: Ubuntu 15.04
  My krilling version is: 58 (rc-proposed)

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

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

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

[Selene Scriven]

Not sure if it helps, but I encountered this using a slightly different
sequence of steps in bug 1569660:  Install uTorch, run it, then try to
grant it permission to access camera-service.  I get a kernel panic
every time, and am never able to grant access.  This was with arale rc-
proposed 304.

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

Title:
  Opening the camera for the first time leads to reboot

Status in camera-app:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Telegram app:
  Invalid
Status in trust-store:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  --

  Same happens with the following steps:

  1. Flash device (arale) with

  $ ubuntu-device-flash touch --device arale --channel ubuntu/rc-
  proposed/meizu.en --recovery-image 
  --bootstrap

  2. Wait until flash process is done
  3. Go through first-start wizard
  4. Pass tutorial
  5. Directly launch camera-app, approve trust-prompt

  Repeat 1-5 multiple times and you will see a frozen device after step
  5. You can verify it happened due to a kernel panic mentioned in
  comment #7.

  You can reset the trust db entry for the camera app using :
  $rm -rf ~/.local/share/CameraService
  $restart cameraservice-trust-stored

  Run the following to get the command line for all threads so you can match 
the pid from the kmsg later (see below):
  ps H -eo 'pid tid cmd:250 comm'

  To verify it was really the kernel panic run

  $ sudo cat /proc/last_kmsg

  once the device has rebooted.

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

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

[Touch-packages] [Bug 1351534] Re: device doesn't detect current time zone

[Selene Scriven]

It's not quite the solution I had in mind, but it does seem like an
improvement.

Other phone platforms automatically pick a relevant time zone any time
the cell radio is turned on, so they get the right time with no
configuration (and update that time automatically during trips, after
each landing).

At the moment, my Ubuntu phones now automatically choose "English (New
Zealand)" or "English (Australia)" as the language, since that's where
my SIM cards are from, but they don't get anywhere near the correct time
until I manually configure "America/Denver" as my time zone.  The
improvement I see is that I no longer have to change this manually in
the settings tool, since it's now one of the OOBE steps.  It also sorts
Denver to the top of the list for "den".

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

Title:
  device doesn't detect current time zone

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

Bug description:
  On first phone boot, or after flashing a new image, the user's time
  zone isn't auto-detected.  Instead, the system always defaults to UTC.

  It should probably default instead to checking the cell provider for
  time zone information, or GPS (if enabled), or if there is a network
  connection, get an approximate location from that (look up the current
  access point, in case it has been mapped).

  I'm not entirely sure which system component or launchpad project this
  belongs in, so some re-targeting help would be appreciated.

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

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

[Touch-packages] [Bug 1564142] Re: Multiple calls to finished/error signals of QNAM object

[Selene Scriven]

Thanks, this appears to fix the incorrect U1 login errors.

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

Title:
  Multiple calls to finished/error signals of QNAM object

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  Recently I've noticed that some odd issues where the
  QNetworkAccessManager API is being used to communicate with REST APIs
  in some of our code. I've tracked this down as far as it seems that
  the finished/error signals seem to get called multiple times,
  sometimes.

  This has resulted in bug #1552546 in ubuntuone-credentials. When
  logging in, if you enter the wrong password, it should show you an
  error message stating that either the email or password was incorrect.
  However, a generic network error message is being shown instead. When
  examining the logs, it seems that the correct error is sent, and then
  an invalid call to the finished signal was made, and a second error
  sent, resulting in the generic network error displayed to the user.
  This same issue happens when the 2FA code is required as well, and a
  network error message is displayed, rather than the 2FA required
  message.

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

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

[Touch-packages] [Bug 1561924] Re: can't scroll to bottom of wifi list in wizard

[Selene Scriven]

No change in krillin rc-proposed 306.  I didn't realize the new wizard
wasn't going to be seen by customers yet.

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

Title:
  can't scroll to bottom of wifi list in wizard

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

Bug description:
  On today's phone image (arale rc-proposed 286), I can't connect to my
  access point in the OOBE wizard because the WAP name starts with a 'w'
  and I can't get the wifi list to scroll all the way to the bottom.

  Any time I get it near the bottom, the list re-shuffles itself and
  scrolls back up.

  Taochen reports seeing the same on a krillin.

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

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

[Touch-packages] [Bug 1563007] Re: App is not installed after credentials are introduced

[Selene Scriven]

I tried to determine when this started happening.

* krillin rc-proposed 270 (2016-03-01): works.
* arale rc-proposed 270 (2016-03-15.1): works.
* krillin rc-proposed 285 (2016-03-17.1): works.
* arale rc-proposed 280 (2016-03-22.0): the app 'install' button appears to do 
nothing at all, except for making the device vibrate a little.
* arale 286 (2016-03-25): works.
* krillin 293 (2016-03-25): works.
* krillin 294 (2016-03-25): works.
* krillin 295 (2016-03-25): works.
* arale 287 (2016-03-26): it stalled at 0% during install on the first try but 
there was no crash.
* krillin 296 (2016-03-26): crashed just after U1 login, but worked when I 
tried on this rev yesterday.
* arale 288 (2016-03-29): crashed just after U1 login.
* arale 289 (2016-03-29): worked (but earlier crashed by simply tapping an app 
to view details).

My conclusion is that the change was most likely sometime in the past few days, 
but the behavior isn't consistent.  I'm not sure why it sometimes works, 
sometimes crashes while loading app details, and sometimes crashes after U1 
login.  Some suspects include:
* https://requests.ci-train.ubuntu.com/#/ticket/1177
* https://code.launchpad.net/~dobey/unity-scope-click/unsign-reviews
* unity-scope-click changed from 0.1.1+15.04.20160321-0ubuntu1 to 
0.1.1+15.04.20160325-0ubuntu1
* pay-ui changed from 15.10+15.04.20160311-0ubuntu1 to 
15.10+15.04.20160324.1-0ubuntu1

http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/296.commitlog
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/287.commitlog

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

Title:
  App is not installed after credentials are introduced

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Remove your Ubuntu One account
  - Go to App Store and select an app to install (e.g. Terminal)
  - Introduce your credentials

  Expected result.
  - App is intalled.

  Actual result.
  - App is not installed

  current build number: 66
  device name: frieza

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

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

[Touch-packages] [Bug 1561924] Re: can't scroll to bottom of wifi list in wizard

[Selene Scriven]

(er, rc-proposed 297, not plain rc)

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

Title:
  can't scroll to bottom of wifi list in wizard

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

Bug description:
  On today's phone image (arale rc-proposed 286), I can't connect to my
  access point in the OOBE wizard because the WAP name starts with a 'w'
  and I can't get the wifi list to scroll all the way to the bottom.

  Any time I get it near the bottom, the list re-shuffles itself and
  scrolls back up.

  Taochen reports seeing the same on a krillin.

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

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

[Touch-packages] [Bug 1563007] Re: App is not installed after credentials are introduced

[Selene Scriven]

FWIW, I'm getting a similar crash on arale rc-proposed 289...  except
the crash happens merely by tapping on an app to view the details.  No
U1 login attempt is required.  I'm not sure if it's the same bug or not,
but it's a crash in the same component.

https://errors.ubuntu.com/oops/8621d07e-f5f4-11e5-9852-fa163e30221b

I think I saw this earlier and thought it was the usual network / server
timeout issue, but a closer look shows it's not.

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

Title:
  App is not installed after credentials are introduced

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Remove your Ubuntu One account
  - Go to App Store and select an app to install (e.g. Terminal)
  - Introduce your credentials

  Expected result.
  - App is intalled.

  Actual result.
  - App is not installed

  current build number: 66
  device name: frieza

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

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

[Touch-packages] [Bug 1563007] Re: App is not installed after credentials are introduced

[Selene Scriven]

I'm accustomed to the store sometimes taking a few tries to install an
app, but this issue is new and leads to the crash as described.

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

Title:
  App is not installed after credentials are introduced

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Remove your Ubuntu One account
  - Go to App Store and select an app to install (e.g. Terminal)
  - Introduce your credentials

  Expected result.
  - App is intalled.

  Actual result.
  - App is not installed

  current build number: 66
  device name: frieza

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

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

[Touch-packages] [Bug 1561924] Re: can't scroll to bottom of wifi list in wizard

[Selene Scriven]

I see this on the latest krillin rc 297.  Since it breaks one of the
main wizard steps, is this a release blocker?

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

Title:
  can't scroll to bottom of wifi list in wizard

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

Bug description:
  On today's phone image (arale rc-proposed 286), I can't connect to my
  access point in the OOBE wizard because the WAP name starts with a 'w'
  and I can't get the wifi list to scroll all the way to the bottom.

  Any time I get it near the bottom, the list re-shuffles itself and
  scrolls back up.

  Taochen reports seeing the same on a krillin.

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

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

[Touch-packages] [Bug 1508262] Re: location-serviced crashes after boot while idle

[Selene Scriven]

I am unable to trigger this any more on current builds.

** Changed in: location-service (Ubuntu)
   Status: New => Fix Released

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

Title:
  location-serviced crashes after boot while idle

Status in location-service package in Ubuntu:
  Fix Released

Bug description:
  Using arale rc-proposed 143, I'm getting location-serviced crashes
  within about 15 minutes each boot if I leave the phone idle.

  Steps to reproduce the issue:
  1. Do a completely fresh wipe/flash of arale rc-proposed 143.
  2. Complete the welcome wizard and scope tutorial.
  3. Tap "skip and set up later" on the Today scope.  After results start to 
load, tap the back button.  I'm not 100% sure if this step is required.
  4. Reboot the phone, then leave it idle without logging in.
  5. Wait ~15 minutes, and check /var/crash periodically.

  Usually, this results in a crash.  Timing varies though.  I've seen it
  happen at 2 minutes and 5 minutes and 15 minutes.

  This phone does not have a SIM card.

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

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

[Touch-packages] [Bug 1561123] Re: Fast scroll letters are blue

[Selene Scriven]

This two-line change appears to do the trick.

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

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

Title:
  Fast scroll letters are blue

Status in Canonical System Image:
  In Progress
Status in address-book-app package in Ubuntu:
  Fix Committed

Bug description:
  After the recent change on SDK pallet the Fast scroll letters became blue. 
  The correct visual is:   letters should be black  and selected letter blue.

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

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

[Touch-packages] [Bug 1557722] Re: address book needs to support rotation

[Selene Scriven]

BTW, while scrolling through a large list of contacts, there is usually
an index on the right side which can provide faster navigation to a
specific letter.  This index doesn't appear in portrait mode.

Could that be added at some point?

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

Title:
  address book needs to support rotation

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  In Progress

Bug description:
  address book is currently locked to portrait and it should not be

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

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

[Touch-packages] [Bug 1560188] [NEW] unity8 hang w/ CPU pegged (needs more detail)

[Selene Scriven]

Public bug reported:

Sometime in the past week or so, it seems that unity8 acquired a new bug
which causes it to use 100% CPU and stop responding.  I saw it happen on
krillin rc-proposed 286 and 288 with silo 39 (address-book-app)
installed.  Jibel saw it with a different silo, and mterry reports
seeing it with yet another different silo.

Details are being collected still, but this bug serves as a place to put
the data together.

For me, the steps involved to trigger it were:
1. Flash rc-proposed to a krillin.
2. Install silo 39, address-book-app, and reboot.  (probably not relevant)
3. Log in, configure time zone, disable automatic updates, configure login to 
use a passcode instead of passphrase, set screen to never turn itself off.
4. Go back to the app scope and launch address-book-app.
5. Tilt the phone to make the screen rotate.

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

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

More details are needed.

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

Title:
  unity8 hang w/ CPU pegged (needs more detail)

Status in unity8 package in Ubuntu:
  New

Bug description:
  Sometime in the past week or so, it seems that unity8 acquired a new
  bug which causes it to use 100% CPU and stop responding.  I saw it
  happen on krillin rc-proposed 286 and 288 with silo 39 (address-book-
  app) installed.  Jibel saw it with a different silo, and mterry
  reports seeing it with yet another different silo.

  Details are being collected still, but this bug serves as a place to
  put the data together.

  For me, the steps involved to trigger it were:
  1. Flash rc-proposed to a krillin.
  2. Install silo 39, address-book-app, and reboot.  (probably not relevant)
  3. Log in, configure time zone, disable automatic updates, configure login to 
use a passcode instead of passphrase, set screen to never turn itself off.
  4. Go back to the app scope and launch address-book-app.
  5. Tilt the phone to make the screen rotate.

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

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

  More details are needed.

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

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

[Touch-packages] [Bug 1559953] [NEW] can't install apps while other account is being added

[Selene Scriven]

Public bug reported:

It looks as if the add-account function can only handle one account at a
time, and cannot be interrupted by other requests.  This can lead to
unexpected behaviors such as:

1. Start with a fresh install, not configured at all.
2. Open the address book app.
3. Tell address book to import contacts from google.
4. While the google login page is visible, switch back to scopes and go to the 
app store.
5. Try to install an app.

Expected result: The 'install' button pops up the U1 login interface,
then installs the app after logging in.

Actual result: The 'install' button does nothing visible to the user,
presumably because the login widget is already busy with a different
account.

This was observed on krillin rc-proposed image 286.

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

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

Title:
  can't install apps while other account is being added

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  It looks as if the add-account function can only handle one account at
  a time, and cannot be interrupted by other requests.  This can lead to
  unexpected behaviors such as:

  1. Start with a fresh install, not configured at all.
  2. Open the address book app.
  3. Tell address book to import contacts from google.
  4. While the google login page is visible, switch back to scopes and go to 
the app store.
  5. Try to install an app.

  Expected result: The 'install' button pops up the U1 login interface,
  then installs the app after logging in.

  Actual result: The 'install' button does nothing visible to the user,
  presumably because the login widget is already busy with a different
  account.

  This was observed on krillin rc-proposed image 286.

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

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

[Touch-packages] [Bug 1559946] [NEW] google login always has "select all" visible

[Selene Scriven]

Public bug reported:

On today's krillin rc-proposed image 286, I noticed that the google
login interface always has "select all" visible while entering text
(even during password entry).  Other text entries do not have this
unless extra functions are requested by holding a while or tapping more
than once.

The UI should probably match the Ubuntu One login interface as closely
as possible, showing extra text options only when requested.  It
probably also shouldn't offer the "select all" option during password
entry.  For U1, this option is greyed out and unresponsive even when
requested.

Screenshot attached.

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Low
 Status: New

** Attachment added: "google-login-always-has-select-all.png"
   
https://bugs.launchpad.net/bugs/1559946/+attachment/4606260/+files/google-login-always-has-select-all.png

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

Title:
  google login always has "select all" visible

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  On today's krillin rc-proposed image 286, I noticed that the google
  login interface always has "select all" visible while entering text
  (even during password entry).  Other text entries do not have this
  unless extra functions are requested by holding a while or tapping
  more than once.

  The UI should probably match the Ubuntu One login interface as closely
  as possible, showing extra text options only when requested.  It
  probably also shouldn't offer the "select all" option during password
  entry.  For U1, this option is greyed out and unresponsive even when
  requested.

  Screenshot attached.

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

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

[Touch-packages] [Bug 1557722] Re: address book needs to support rotation

[Selene Scriven]

There is progress (in silo 039 / https://requests.ci-
train.ubuntu.com/#/ticket/1130 ), but it's not quite there yet...  look
what happens if it's rotated immediately:

** Attachment added: "first-run-layout-fail.png"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557722/+attachment/4606247/+files/first-run-layout-fail.png

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

Title:
  address book needs to support rotation

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  In Progress

Bug description:
  address book is currently locked to portrait and it should not be

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

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

[Touch-packages] [Bug 1385370] Re: second video playback has sound but no visuals

[Selene Scriven]

Indeed, this is fixed.  Has been for quite a while.

** Changed in: gallery-app (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  second video playback has sound but no visuals

Status in gallery-app package in Ubuntu:
  Fix Released

Bug description:
  I'm not entirely sure if this is caused by gallery itself or an
  underlying component, but if I play a video in the gallery app, allow
  it to finish, then play it again, there is sound but no video.

  To reproduce this behavior, do not return to the gallery's list view
  after playback ends.  Simply tap a blank part of the screen to bring
  up the transport controls, and tap 'play' to start the video again.

  If I hit "< / back" to return to the list view between showings, the
  video is able to play correctly each time (except for Bug 1378311,
  which is now fixed).

  This was on krillin rtm image 124, and the video I used for testing
  was the Tears of Steel video from our MWC demo earlier this year.

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

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

[Touch-packages] [Bug 1374662] Re: crash while scrolling and stressing thumbnailer

[Selene Scriven]

I haven't been able to trigger this issue for quite a while, so I'm
assuming it's fixed.

** Changed in: gallery-app (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  crash while scrolling and stressing thumbnailer

Status in gallery-app package in Ubuntu:
  Fix Released

Bug description:
  I got a crash in the gallery app today, on krillin rtm image 69 with
  silo rtm/landing-009 installed (unity-system-compositor).

  I'm not sure if it's related to the silo or not, or whether it's
  reproducible, but I at least have the crash dump.

  At the time, I was running gallery for the first time after preloading
  the phone with photos and videos.  I scrolled rapidly up and down
  while the thumbnails were being generated, to see if I could trigger
  thumbnail creation for as many images as possible.  After a few
  seconds, gallery locked up, dumped via apport, then died.

  The crash dump and a screen shot of its final state are attached.

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

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

[Touch-packages] [Bug 1302004] Re: Indicator-datetime doesn't list in-progress events

[Selene Scriven]

This behavior isn't always a bad thing.  It might be good to make it a
configurable option, since people sometimes want to see in-progress
events and sometimes don't.  The widget I use on other devices has an
option to remove events on end rather than on start, show or hide all-
day events, highlight in-progress events, use different colors for items
from different calendars, and quite a few other things.

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

Title:
  Indicator-datetime doesn't list in-progress events

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

  : "If there are more
  than five, the events shown should be, in order of priority, * any
  events that start or end (a) for today, after the current minute, or
  (b) for any other date, at any time on that date, * any full-day
  events that span all of the selected date..."

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

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

[Touch-packages] [Bug 1557571] Re: Upcoming event ETA appears to fall out of sync

[Selene Scriven]

Thanks for adding this.  It's not a huge deal, but it would be nice if
it updated a little more often during the last hour or so before an
event starts.

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

Title:
  Upcoming event ETA appears to fall out of sync

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Described by ToyKeeper @ https://trello.com/c/S0yjk9mW/2892-893
  -ubuntu-landing-003-indicator-datetime-dbarth:

  > Also, the indicator sometimes gets the wrong time until an event is
  scheduled to start. As an example, I had an event scheduled for 23:50.
  At 23:43 I pulled down the indicator and it said 7 minutes 'till. At
  23:45 I tried again and it still said 7 minutes. I checked again at
  23:47 and it said 3 minutes till. I checked again at 23:50 and it
  still said 3 minutes. At 23:51 the item disappeared, even though the
  event was an hour long. So, it updates infrequently and doesn't show
  events while they're active (except for the first minute).

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

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

[Touch-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

[Selene Scriven]

Yes, this still happens with today's phone image.  It took about a dozen
power cycles to trigger.

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

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

Title:
  power cycling Emerson EM229 headset caused phone to reboot

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

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com;] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com;] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

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

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

[Touch-packages] [Bug 1515816] Re: [messaging app] selected SIM hard for some people to see

[Selene Scriven]

The new theme uses light blue versus grey instead of the older dark red
vs black.  This is easier for red-colorblind people to distinguish, but
it might still be nice to have a change beyond just the color, like a
thicker underline or something.  Some are more colorblind than others.

** Attachment added: "screenshot20160314_214602109.png"
   
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1515816/+attachment/4599507/+files/screenshot20160314_214602109.png

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

Title:
  [messaging app] selected SIM hard for some people to see

Status in Ubuntu UX:
  Incomplete
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  To indicate which SIM slot is active, the messaging-app changes the
  SIM label from black-on-white to dark-red-on-white.  For red-
  colorblind people, this highlight makes no significant difference.
  Studies estimate that this affects about 8% of the male population and
  about 0.5% of the female population.

  Could the visual change be made slightly more noticeable?  Perhaps
  only underline the active slot, or render the active slot in a bold
  font, or maybe change the color to something with higher contrast
  compared to the inactive slot?

  A screenshot is attached.  The top row shows no SIM selected, while
  the second row shows SIM 2 selected.  To red-colorblind people, they
  look nearly identical.

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

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

[Touch-packages] [Bug 1515816] Re: [messaging app] selected SIM hard for some people to see

[Selene Scriven]

Olga isn't with Canonical any more, and the theme has changed since I
filed this bug.  Needs re-testing and possibly re-assignment.

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

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

Title:
  [messaging app] selected SIM hard for some people to see

Status in Ubuntu UX:
  Incomplete
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  To indicate which SIM slot is active, the messaging-app changes the
  SIM label from black-on-white to dark-red-on-white.  For red-
  colorblind people, this highlight makes no significant difference.
  Studies estimate that this affects about 8% of the male population and
  about 0.5% of the female population.

  Could the visual change be made slightly more noticeable?  Perhaps
  only underline the active slot, or render the active slot in a bold
  font, or maybe change the color to something with higher contrast
  compared to the inactive slot?

  A screenshot is attached.  The top row shows no SIM selected, while
  the second row shows SIM 2 selected.  To red-colorblind people, they
  look nearly identical.

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

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

[Touch-packages] [Bug 1351534] Re: device doesn't detect current time zone

[Selene Scriven]

There was a branch linked in early December, but then holidays happened.
Is this still active?

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

Title:
  device doesn't detect current time zone

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

Bug description:
  On first phone boot, or after flashing a new image, the user's time
  zone isn't auto-detected.  Instead, the system always defaults to UTC.

  It should probably default instead to checking the cell provider for
  time zone information, or GPS (if enabled), or if there is a network
  connection, get an approximate location from that (look up the current
  access point, in case it has been mapped).

  I'm not entirely sure which system component or launchpad project this
  belongs in, so some re-targeting help would be appreciated.

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

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

[Touch-packages] [Bug 1453289] Re: network-manager asks for passwords it already knows

[Selene Scriven]

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

** This bug has been marked a duplicate of bug 615239
   Every Wi-Fi disconnection is treated as an authentication error

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

Title:
  network-manager asks for passwords it already knows

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Network Manager (and the network indicator) asks for
  passwords it already knows.  This issue is intermittent and I'm not
  yet sure what causes it, but it has been happening for a long time on
  many different devices.

  I'm seeing it happen in Ubuntu Touch on krillin (rtm 274, OTA3.5
  candidate), but also on every other Ubuntu Touch device I've ever used
  and every notebook I've ever tried Network Manager on.  This bug is
  specifically targeting Ubuntu Touch though.

  The issue is easiest to trigger by rebooting the phone.  While
  developing a new reboot loop test, I saw this happen on 8 of 12 boots
  during a short test sequence.  The logs from that are attached, though
  I'm not sure if it contains nearly enough information.

  Triggering the issue is sometimes difficult due to the intermittent
  nature, but in general it usually happens if I leave a device idle
  overnight.  In the morning I'm greeted by a dialog asking for my wifi
  password.  If I cancel the dialog it will connect successfully (though
  sometimes I also have to drag down the indicator and tap the network
  to tell it to connect), so it hasn't forgotten the password.

  If more logs are needed, let me know which ones and I can add them to
  the test.

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

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

[Touch-packages] [Bug 1544033] Re: Account details page needs design love

[Selene Scriven]

The empty space seems fixed in silo 77 (ticket 1003) today, but not the
icon or name.

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

Title:
  Account details page needs design love

Status in Online Accounts setup for Ubuntu Touch:
  In Progress
Status in Ubuntu UX:
  New
Status in webapps-sprint:
  In Progress
Status in pay-ui package in Ubuntu:
  Invalid
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

Bug description:
  See attached screenshot. There's multiple issues with this page:

  * Empty space at the top
  * missing icon for PayUI
  * PayUI displays appid instead of user friendly name

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

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

[Touch-packages] [Bug 1554254] Re: /usr/bin/online-accounts-ui:11:strlen:QByteArray::QByteArray:Accounts::Provider::domDocument:OnlineAccountsUi::ApplicationManager::providerInfo:OnlineAccountsUi::Pro

[Selene Scriven]

A fix should be landing via silo 77 (ticket 1003), but I haven't been
able to trigger the original conditions to test it.

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

Title:
  /usr/bin/online-accounts-
  
ui:11:strlen:QByteArray::QByteArray:Accounts::Provider::domDocument:OnlineAccountsUi::ApplicationManager::providerInfo:OnlineAccountsUi::ProviderRequestPrivate::start

Status in webapps-sprint:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

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

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

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

[Touch-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

[Selene Scriven]

I'm not sure why this is marked as incomplete now.  Has the new upstream
kernel made it into our devices?  Is a fix included and ready to test?

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

** Changed in: bluez (Ubuntu)
 Assignee: Selene Scriven (toykeeper) => Tony Espy (awe)

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

Title:
  power cycling Emerson EM229 headset caused phone to reboot

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com;] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com;] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

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

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

[Touch-packages] [Bug 1373463] Re: [indicators] Impossible to disable cellular data from indicator

[Selene Scriven]

There are versions of Android without cell data in the quick toggles?
Wild.

Every Android device I've tried had it, and usually in more than one
convenient place.  Like one which pulls down from the top bar, one in a
toggle rack which can be placed on a desktop, etc.  Ubuntu doesn't have
desktop widgets, but it could still go in the top bar pull-down area.
Sometimes tapping it only toggles data, sometimes it toggles
2G/3G/4G/off, sometimes it toggles calls+data, calls-only, or no cell
radio.  Sometimes holding it brings up the cell settings menu, sometimes
holding it brings up traffic accounting, sometimes holding it brings up
the widget UI config tool.

It might be a common expectation for Ubuntu to have something similar.

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

Title:
  [indicators] Impossible to disable cellular data from indicator

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

Bug description:
  I was wondering : Why it isn't possible to disable data from the
  network indicator ? Probably with a switch button that offer the
  choice between no data or data activated (with the last data activated
  state (2g only or 2G,3G,4G).

  Why this ? Because it's the first setting to change to save battery,
  and probably one of the most used (I asked around me, everyone agreed
  they would prefer that over Wi-Fi if only one was possible).

  I think it's stupid to go to the settings app for the most common
  action (and very frustrating). Of course, this also apply for the
  battery setting page (that already contain Wi-Fi, GPS, Bluetooth and
  brightness settings).

  I asked that on the phone ML, I've been invited to file a wishlist bug
  there to "help" designers with next iteration of network indicator. So
  here it is !

  [1] : mailing list discussion with already some support to this idea :
  https://lists.launchpad.net/ubuntu-phone/msg09910.html

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

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

[Touch-packages] [Bug 1373463] Re: [indicators] Impossible to disable cellular data from indicator

[Selene Scriven]

Just a +1 for this feature.

My preferred default phone state is to turn on calls and sms, but turn
off all other radios (cell data, wifi, bluetooth, gps, etc).  It'd be
nice to be able to quickly turn cell data on for the few minutes at a
time when I actually want it, then quickly turn it off again.  I don't
particularly want the phone doing anything online when I haven't
requested it.

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

Title:
  [indicators] Impossible to disable cellular data from indicator

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

Bug description:
  I was wondering : Why it isn't possible to disable data from the
  network indicator ? Probably with a switch button that offer the
  choice between no data or data activated (with the last data activated
  state (2g only or 2G,3G,4G).

  Why this ? Because it's the first setting to change to save battery,
  and probably one of the most used (I asked around me, everyone agreed
  they would prefer that over Wi-Fi if only one was possible).

  I think it's stupid to go to the settings app for the most common
  action (and very frustrating). Of course, this also apply for the
  battery setting page (that already contain Wi-Fi, GPS, Bluetooth and
  brightness settings).

  I asked that on the phone ML, I've been invited to file a wishlist bug
  there to "help" designers with next iteration of network indicator. So
  here it is !

  [1] : mailing list discussion with already some support to this idea :
  https://lists.launchpad.net/ubuntu-phone/msg09910.html

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

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

[Selene Scriven]

tvoss: The raw data is available.  Simply remove "graph.png" from the
URL and it'll give you a directory with all sorts of logs.

The green-shaded section is the active measurement period used for
statistics.  The red-shaded portions indicate where USB was connected.
Everything else is unplugged.

-- 
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:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

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 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Selene Scriven]

FWIW, I see the weird new behavior on every test with wifi enabled, even
when the screen is on and the phone is actively doing something.  For
example, while playing music:

http://people.canonical.com/~platform-qa/power-
results/2015-12-08_09:19:36-krillin-196-power_usage_music/graph.png

... versus how it looked before:

http://people.canonical.com/~platform-qa/power-
results/2015-12-08_04:50:02-krillin-195-power_usage_music/graph.png

But in flight mode, both graphs are a flat line barely above zero:

http://people.canonical.com/~platform-qa/power-
results/2015-12-08_11:07:01-krillin-196-power_usage_flight_mode_on/graph.png

So, it's not just while sleeping; it's any time wifi is enabled.

-- 
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:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

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 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Selene Scriven]

Is it possible that this fix might cause a phone to wake up more often,
or to stay awake longer?  I'm seeing weird idle power behavior ever
since this fix landed in krillin rc-proposed 196.

Before: ~9 mA
http://people.canonical.com/~platform-qa/power-results/2015-12-08_03:19:30-krillin-195-power_usage_idle/graph.png

After: ~35 mA
http://people.canonical.com/~platform-qa/power-results/2015-12-08_07:36:16-krillin-196-power_usage_idle/graph.png

Here's the commit log for 196:

http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-
proposed/196.commitlog

Arale results look fine.  I don't know why krillin is different, but I'm
only seeing this behavior on krillin when wifi is connected...  and this
bug fix is a likely suspect.  I don't see additional forks or crashes in
the test logs, which suggests the issue is probably caused by a long-
running process.

-- 
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:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

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 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Selene Scriven]

I created bug 1524133 to track the issues I'm seeing.  I don't know if
it's related to this bug, but so far it looks probable.

-- 
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:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

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 1385358] Re: crash while pushing videos to device

[Selene Scriven]

The tarball I mentioned earlier is:
http://toykeeper.net/tmp/phablet/videos.tgz

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

Title:
  crash while pushing videos to device

Status in mediascanner2 package in Ubuntu:
  Incomplete

Bug description:
  I consistently get a mediascanner crash when I push videos to my
  device after flashing it.  These are the commands I run to send the
  videos:

  adb push ~/.cache/mwc/videos.tgz /home/phablet/Videos
  adb shell 'cd /home/phablet/Videos && tar xfvz videos.tgz && rm -f videos.tgz'

  The crash happens during the second command, extracting or removing
  the tarball.  The video tarball itself is the same one we used for the
  MWC demo a long time ago.

  The resulting crash file is attached.

  I recall seeing this frequently for a long time, but the crash file I
  attached is based on krillin-proposed rtm image 124.

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

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

[Touch-packages] [Bug 1385358] Re: crash while pushing videos to device

[Selene Scriven]

Sorry for the delays, I had forgotten about this bug.

I tested again today (arale rc-proposed 174) and it appears to still
happen.  I don't recall seeing it via MTP, but that's not automated so
the MTP case isn't touched as often.  Attempting it just now, I didn't
get it to fail...  but sending via mtp is also a lot slower than
untarring a file locally on the phone so it might not stress the device
much.

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

Title:
  crash while pushing videos to device

Status in mediascanner2 package in Ubuntu:
  Incomplete

Bug description:
  I consistently get a mediascanner crash when I push videos to my
  device after flashing it.  These are the commands I run to send the
  videos:

  adb push ~/.cache/mwc/videos.tgz /home/phablet/Videos
  adb shell 'cd /home/phablet/Videos && tar xfvz videos.tgz && rm -f videos.tgz'

  The crash happens during the second command, extracting or removing
  the tarball.  The video tarball itself is the same one we used for the
  MWC demo a long time ago.

  The resulting crash file is attached.

  I recall seeing this frequently for a long time, but the crash file I
  attached is based on krillin-proposed rtm image 124.

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

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

[Touch-packages] [Bug 1385358] Re: crash while pushing videos to device

[Selene Scriven]

** Attachment added: 
"_usr_lib_arm-linux-gnueabihf_mediascanner-2.0_mediascanner-extractor.32011.crash"
   
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1385358/+attachment/4522401/+files/_usr_lib_arm-linux-gnueabihf_mediascanner-2.0_mediascanner-extractor.32011.crash

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

Title:
  crash while pushing videos to device

Status in mediascanner2 package in Ubuntu:
  Incomplete

Bug description:
  I consistently get a mediascanner crash when I push videos to my
  device after flashing it.  These are the commands I run to send the
  videos:

  adb push ~/.cache/mwc/videos.tgz /home/phablet/Videos
  adb shell 'cd /home/phablet/Videos && tar xfvz videos.tgz && rm -f videos.tgz'

  The crash happens during the second command, extracting or removing
  the tarball.  The video tarball itself is the same one we used for the
  MWC demo a long time ago.

  The resulting crash file is attached.

  I recall seeing this frequently for a long time, but the crash file I
  attached is based on krillin-proposed rtm image 124.

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

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

[Touch-packages] [Bug 1385358] Re: crash while pushing videos to device

[Selene Scriven]

** Attachment added: "mediascanner-2.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1385358/+attachment/4522400/+files/mediascanner-2.0.log

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

Title:
  crash while pushing videos to device

Status in mediascanner2 package in Ubuntu:
  Incomplete

Bug description:
  I consistently get a mediascanner crash when I push videos to my
  device after flashing it.  These are the commands I run to send the
  videos:

  adb push ~/.cache/mwc/videos.tgz /home/phablet/Videos
  adb shell 'cd /home/phablet/Videos && tar xfvz videos.tgz && rm -f videos.tgz'

  The crash happens during the second command, extracting or removing
  the tarball.  The video tarball itself is the same one we used for the
  MWC demo a long time ago.

  The resulting crash file is attached.

  I recall seeing this frequently for a long time, but the crash file I
  attached is based on krillin-proposed rtm image 124.

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

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

[Touch-packages] [Bug 1351299] Re: [Location Indicator Menu] GPS switch should be turned off when "Location detection" is off

[Selene Scriven]

While this technically closes the bug, it also makes location controls
less convenient and harder to access.  Would it be possible to have the
control in both the indicator and in system settings, in addition to the
new link in the indicator?  Is there a way to do a 3-way toggle in the
indicator?  (off / gps-only / full)

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

Title:
  [Location Indicator Menu] GPS switch should be turned off when
  "Location detection" is off

Status in Canonical System Image:
  Triaged
Status in Ubuntu UX:
  Fix Committed
Status in indicator-location package in Ubuntu:
  Fix Committed
Status in location-service package in Ubuntu:
  Incomplete
Status in trust-store package in Ubuntu:
  Incomplete
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  After a conversation with tvoss, I understand that if I turn the
  "Location detection" switch off, effectively GPS will be turned off
  too.

  However, the two switches are independent: I can switch "Location
  detection" off and the "GPS" switch will stay on. This might be
  confusing for users: I'd expect both switches to go off when turning
  "Location detection" off.

  
  -- UX Comment --

  Location section in the Indicators spec has been updated with latest
  visuals and desired behaviour.

  On tap of 'Location settings...', users can choose to use 'GPS only'
  (without using Here services) in the relevant System settings screen.

  
https://docs.google.com/document/edit?hgd=1=1810KDpFl2Mxsn1z3wehPU9pkbS6R6o-j1-pmYpkYb7A#heading=h.jh8j7gb6bo0s

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

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

[Touch-packages] [Bug 1515816] [NEW] selected SIM hard for some people to see

[Selene Scriven]

Public bug reported:

To indicate which SIM slot is active, the messaging-app changes the SIM
label from black-on-white to dark-red-on-white.  For red-colorblind
people, this highlight makes no significant difference.  Studies
estimate that this affects about 8% of the male population and about
0.5% of the female population.

Could the visual change be made slightly more noticeable?  Perhaps only
underline the active slot, or render the active slot in a bold font, or
maybe change the color to something with higher contrast compared to the
inactive slot?

A screenshot is attached.  The top row shows no SIM selected, while the
second row shows SIM 2 selected.  To red-colorblind people, they look
nearly identical.

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

** Attachment added: "sim-selected.png"
   
https://bugs.launchpad.net/bugs/1515816/+attachment/4517904/+files/sim-selected.png

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

Title:
  selected SIM hard for some people to see

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  To indicate which SIM slot is active, the messaging-app changes the
  SIM label from black-on-white to dark-red-on-white.  For red-
  colorblind people, this highlight makes no significant difference.
  Studies estimate that this affects about 8% of the male population and
  about 0.5% of the female population.

  Could the visual change be made slightly more noticeable?  Perhaps
  only underline the active slot, or render the active slot in a bold
  font, or maybe change the color to something with higher contrast
  compared to the inactive slot?

  A screenshot is attached.  The top row shows no SIM selected, while
  the second row shows SIM 2 selected.  To red-colorblind people, they
  look nearly identical.

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

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

[Touch-packages] [Bug 1508260] [NEW] un-starring a scope jumps several scopes to the right

[Selene Scriven]

Public bug reported:

When I tap the star in a scope to un-favorite it, the view spontaneously
shifts several scopes to the right.  For example, if I flash a
completely fresh image (such as arale rc-proposed 143), boot the first
time, and tap the Today scope's star, the view shifts to the News scope
instead of the Nearby scope.

In older images, the view would shift only to the nearest neighbor,
preferring right-most when one existed.

Could we revert this back to the older behavior?  Skipping multiple
scopes seems like a bug.

** Affects: unity-scopes-shell (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  un-starring a scope jumps several scopes to the right

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

Bug description:
  When I tap the star in a scope to un-favorite it, the view
  spontaneously shifts several scopes to the right.  For example, if I
  flash a completely fresh image (such as arale rc-proposed 143), boot
  the first time, and tap the Today scope's star, the view shifts to the
  News scope instead of the Nearby scope.

  In older images, the view would shift only to the nearest neighbor,
  preferring right-most when one existed.

  Could we revert this back to the older behavior?  Skipping multiple
  scopes seems like a bug.

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

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

[Touch-packages] [Bug 1508262] Re: location-serviced crashes after boot while idle

[Selene Scriven]

** Attachment added: "_usr_bin_ubuntu-location-serviced.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1508262/+attachment/4501469/+files/_usr_bin_ubuntu-location-serviced.0.crash

** Description changed:

  Using arale rc-proposed 143, I'm getting location-serviced crashes
  within about 15 minutes each boot if I leave the phone idle.
  
  Steps to reproduce the issue:
- 1. Do a completely fresh flash of arale rc-proposed 143.
+ 1. Do a completely fresh wipe/flash of arale rc-proposed 143.
  2. Complete the welcome wizard and scope tutorial.
- 3. Tap "skip and set up later" on the Today scope.
- 4. Reboot the phone.
+ 3. Tap "skip and set up later" on the Today scope.  After results start to 
load, tap the back button.  I'm not 100% sure if this step is required.
+ 4. Reboot the phone, then leave it idle without logging in.
  5. Wait ~15 minutes, and check /var/crash periodically.
+ 
+ Usually, this results in a crash.  Timing varies though.  I've seen it
+ happen at 2 minutes and 5 minutes and 15 minutes.
+ 
+ This phone does not have a SIM card.

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

Title:
  location-serviced crashes after boot while idle

Status in location-service package in Ubuntu:
  New

Bug description:
  Using arale rc-proposed 143, I'm getting location-serviced crashes
  within about 15 minutes each boot if I leave the phone idle.

  Steps to reproduce the issue:
  1. Do a completely fresh wipe/flash of arale rc-proposed 143.
  2. Complete the welcome wizard and scope tutorial.
  3. Tap "skip and set up later" on the Today scope.  After results start to 
load, tap the back button.  I'm not 100% sure if this step is required.
  4. Reboot the phone, then leave it idle without logging in.
  5. Wait ~15 minutes, and check /var/crash periodically.

  Usually, this results in a crash.  Timing varies though.  I've seen it
  happen at 2 minutes and 5 minutes and 15 minutes.

  This phone does not have a SIM card.

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

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

[Touch-packages] [Bug 1508262] [NEW] location-serviced crashes after boot while idle

[Selene Scriven]

Public bug reported:

Using arale rc-proposed 143, I'm getting location-serviced crashes
within about 15 minutes each boot if I leave the phone idle.

Steps to reproduce the issue:
1. Do a completely fresh wipe/flash of arale rc-proposed 143.
2. Complete the welcome wizard and scope tutorial.
3. Tap "skip and set up later" on the Today scope.  After results start to 
load, tap the back button.  I'm not 100% sure if this step is required.
4. Reboot the phone, then leave it idle without logging in.
5. Wait ~15 minutes, and check /var/crash periodically.

Usually, this results in a crash.  Timing varies though.  I've seen it
happen at 2 minutes and 5 minutes and 15 minutes.

This phone does not have a SIM card.

** Affects: location-service (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  location-serviced crashes after boot while idle

Status in location-service package in Ubuntu:
  New

Bug description:
  Using arale rc-proposed 143, I'm getting location-serviced crashes
  within about 15 minutes each boot if I leave the phone idle.

  Steps to reproduce the issue:
  1. Do a completely fresh wipe/flash of arale rc-proposed 143.
  2. Complete the welcome wizard and scope tutorial.
  3. Tap "skip and set up later" on the Today scope.  After results start to 
load, tap the back button.  I'm not 100% sure if this step is required.
  4. Reboot the phone, then leave it idle without logging in.
  5. Wait ~15 minutes, and check /var/crash periodically.

  Usually, this results in a crash.  Timing varies though.  I've seen it
  happen at 2 minutes and 5 minutes and 15 minutes.

  This phone does not have a SIM card.

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

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

[Touch-packages] [Bug 1476476] Re: battery indicator only sort of reflects actual battery charge

[Selene Scriven]

Yes, please attach those screenshots, along with a description of what
happened in each.  :)

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

Title:
  battery indicator only sort of reflects actual battery charge

Status in Canonical System Image:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  On Ubuntu Touch devices, the battery indicator and graph behave in
  strange ways which do not accurately represent the state of the
  phone's battery or power supply.  This may be several bugs, but more
  than one of those can probably be fixed in a single straightforward
  way.

  Attached is a graph showing, at the top, what the battery indicator
  and graph show.  Below, the blue line shows the kernel's voltage value
  from /sys/class/power_supply/battery/voltage_now , and the green line
  shows the actual voltage going in to the phone from a power supply.

  To help make sense of the graph, here are the events which happened during 
the measurement period:
  - I tested bug 1476468, but this part of the graph is cut off to the left.
  - I turned the power supply up to 4.2X V and turned the phone back on.  It 
was not plugged in to USB.
  - At about 0.1 hours I turned the power supply down to 3.1V and waited.
  - At about 0.35 hours the phone turned itself off; I guess I set the input 
power too low.
  - At about 0.45 hours I noticed, turned the power up to 4.3V, and turned the 
phone back on.  After it booted, I turned the power down to 3.3V and waited 
again.
  - Time passed; I was working on other things.
  - At ~2.7 hours, I turned up the power supply to 4.3 V.
  - At ~2.8 hours, I plugged in USB.
  - At ~3.8 hours, the battery indicator noticed, jumped to 85%, and 
retroactively changed the graph from a horizontal line to a diagonal rising 
line.

  One issue is that the user-visible graph lags way behind the power
  supply.  It took about 35 to 60 minutes to notice that the power had
  dropped to a very low level, then plummeted all at once.  Before this,
  it merely declined a few percent.  The kernel's reading also lags a
  bit, but it looks like it may simply have a lowpass filter or
  something on it.  Regardless, the kernel's raw value is much closer to
  reality.

  A second issue is that the user-visible graph and percent do not go up
  when the battery voltage increases.  It refuses to increase the
  estimated charge, ever, unless USB is plugged in.  However, li-ion
  batteries normally recover some voltage after a high-amperage drain
  stops.  So, if you watch videos for half an hour and stop, the charge
  actually recovers and the battery indicator should reflect this.
  Letting the percent go up while it's not plugged in is not an error,
  it's just how the battery works.

  A third (and fourth) issue is that it took about an hour for the
  indicator to show an increased charge even after the USB cable was
  plugged in.  ...  and then despite jumping suddenly from 1% to 85% it
  *retroactively* changed the graph to make it look like the level had
  been increasing the whole time.

  I notice that the kernel sees voltage increases immediately, but
  decreases take a while to settle.  Not ideal, but probably not bad
  either.

  What I propose as a solution: Instead of using the current code to
  estimate a charge percent, we should perhaps translate the kernel's
  voltage value into a percent directly.  At least while unplugged.
  While plugged in, I'm not sure if the kernel has an accurate value
  anywhere.  Using the kernel data directly would give a more accurate
  representation of the battery state, and is not prone to the bizarre
  behaviors reported on the mailing lists (or the corner cases I've
  observed in testing on a modified phone).

  As for translating the kernel voltage into a percent, it simply needs to go 
through a curve correction function.  It should look approximately like one of 
these, depending on the exact battery type:
  http://www.lygte-info.dk/pic/Batteries2011/All18650/Capacity-0.2A.png

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

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

[Touch-packages] [Bug 615239] Re: Every Wi-Fi disconnection is treated as an authentication error

[Selene Scriven]

Any reason why this bug is marked as wishlist?

It has been failing for many years, and continues to be somewhere
between an inconvenience and a headache.  I keep running into it lately
because it breaks automated tests or makes them unreliable.

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

Title:
  Every Wi-Fi disconnection is treated as an authentication error

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  I'm using lucid, with the 0.8-0ubuntu3, in a laptop, and is incredible that 
the nm-applet couldn't diagnostic why the wireless connection was lost and only 
trow the password prompt when I've lost the signal. nm-applet should see the 
kern.log or dmesg to react at signal lost. For example, when the kernel try 3 
times probe the AP and don't get response nm-applet say The pc are far away 
from the access point and can not be connected. Please, move close to the 
access point or try another more near. And by the way, when the authentication 
fails, or the association.
  --- 
  Architecture: i386
  CRDA: Error: [Errno 2] No existe el archivo o directorio
  CheckboxSubmission: ee8ebec101005ce57a9c3355b36ca8a7
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  DistroRelease: Ubuntu 10.04
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  IpRoute:
   172.16.254.0/24 dev wlan1  proto kernel  scope link  src 172.16.254.5  
metric 2 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   default via 172.16.254.200 dev wlan1  proto static
  Keyfiles: Error: [Errno 2] No existe el archivo o directorio
  Package: network-manager 0.8-0ubuntu3
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_DO.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags: lucid
  Uname: Linux 2.6.32-24-generic i686
  UserGroups:

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

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

[Touch-packages] [Bug 1453289] Re: network-manager asks for passwords it already knows

[Selene Scriven]

** Tags added: power-bugs

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

Title:
  network-manager asks for passwords it already knows

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Network Manager (and the network indicator) asks for
  passwords it already knows.  This issue is intermittent and I'm not
  yet sure what causes it, but it has been happening for a long time on
  many different devices.

  I'm seeing it happen in Ubuntu Touch on krillin (rtm 274, OTA3.5
  candidate), but also on every other Ubuntu Touch device I've ever used
  and every notebook I've ever tried Network Manager on.  This bug is
  specifically targeting Ubuntu Touch though.

  The issue is easiest to trigger by rebooting the phone.  While
  developing a new reboot loop test, I saw this happen on 8 of 12 boots
  during a short test sequence.  The logs from that are attached, though
  I'm not sure if it contains nearly enough information.

  Triggering the issue is sometimes difficult due to the intermittent
  nature, but in general it usually happens if I leave a device idle
  overnight.  In the morning I'm greeted by a dialog asking for my wifi
  password.  If I cancel the dialog it will connect successfully (though
  sometimes I also have to drag down the indicator and tap the network
  to tell it to connect), so it hasn't forgotten the password.

  If more logs are needed, let me know which ones and I can add them to
  the test.

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

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

[Touch-packages] [Bug 1453289] Re: network-manager asks for passwords it already knows

[Selene Scriven]

I've noticed this also interferes sometimes with automated power testing.  For 
example, these two test runs were invalid because of the NM bug:
http://people.canonical.com/~platform-qa/power-results/2015-07-09_21:38:21-arale-55-power_usage_idle/8/
http://people.canonical.com/~platform-qa/power-results/2015-07-16_23:25:17-arale-61-power_usage_display_on/2/

The more recent one has more logs and thus might have more useful
information.

I've seen this bug on every NetworkManager-based system I've ever tried,
not just Ubuntu, and it has been one of my top reasons for not using
NetworkManager.  It's really unfortunate that the bug made it all the
way to the Ubuntu phone, after not getting fixed for approximately a
decade.

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

Title:
  network-manager asks for passwords it already knows

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Network Manager (and the network indicator) asks for
  passwords it already knows.  This issue is intermittent and I'm not
  yet sure what causes it, but it has been happening for a long time on
  many different devices.

  I'm seeing it happen in Ubuntu Touch on krillin (rtm 274, OTA3.5
  candidate), but also on every other Ubuntu Touch device I've ever used
  and every notebook I've ever tried Network Manager on.  This bug is
  specifically targeting Ubuntu Touch though.

  The issue is easiest to trigger by rebooting the phone.  While
  developing a new reboot loop test, I saw this happen on 8 of 12 boots
  during a short test sequence.  The logs from that are attached, though
  I'm not sure if it contains nearly enough information.

  Triggering the issue is sometimes difficult due to the intermittent
  nature, but in general it usually happens if I leave a device idle
  overnight.  In the morning I'm greeted by a dialog asking for my wifi
  password.  If I cancel the dialog it will connect successfully (though
  sometimes I also have to drag down the indicator and tap the network
  to tell it to connect), so it hasn't forgotten the password.

  If more logs are needed, let me know which ones and I can add them to
  the test.

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

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

[Touch-packages] [Bug 1475528] Re: maliit-server crashes during power tests

[Selene Scriven]

Sometimes unity8 also crashes, but usually not.  If you look at the
links above you can see what other crash dumps there were for each test
run.  Also, bug 1475526 may be of interest since it now looks like it
might be the same root cause.

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

Title:
  maliit-server crashes during power tests

Status in maliit-framework package in Ubuntu:
  New

Bug description:
  Maliit-server crashes fairly often while running power usage tests. I
  hope someone will be able to determine the root cause based on crash
  dumps and other logs.

  Here are some of the 128 instances I've seen so far... inside each are
  numbered directories for each test run, and the crash dumps are inside
  of those under var-crash/ .

  Arale rc-proposed 60, runs 3, 4, 5, and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_13:26:50-arale-60-power_usage_idle/

  Arale devel-proposed 61, runs 2 and 3:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

  Krillin rc-proposed 62, run 4:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_03:46:40-krillin-62-power_usage_display_on/

  Krillin rc-proposed 62, runs 4 and 5:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_02:02:39-krillin-62-power_usage_idle/

  These are merely samples from recent test runs. I have plenty more if
  you need them, or can add additional logging to get more data from
  future tests.

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

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

[Touch-packages] [Bug 1475523] [NEW] frequent unity8 crashes during power tests

[Selene Scriven]

Public bug reported:

Unity8 crashes fairly often while running power usage tests.  I don't
know what causes it, but I've collected a lot of data during the test
runs and I hope someone will be able to make sense of the crash dumps
and other logs.

Here are some of the 162 instances I've seen so far...  inside each are
numbered directories for each test run, and the crash dumps are inside
of those under var-crash/ .

Arale rc-proposed 61, runs 3 and 4:
http://people.canonical.com/~platform-qa/power-results/2015-07-16_18:21:18-arale-61-power_usage_display_on/

Arale devel-proposed 61, runs 1, 2, and 5:
http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

Krillin rc-proposed 65, runs 2 and 7:
http://people.canonical.com/~platform-qa/power-results/2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/

Krillin devel-proposed, runs 1 and 7:
http://people.canonical.com/~platform-qa/power-results/2015-07-13_22:02:04-krillin-132-power_usage_display_on/

These are merely samples from recent test runs.  I've been seeing the
crashes regularly ever since I started tracking crash dump files on July
3.

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


** Tags: power-bugs

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

Title:
  frequent unity8 crashes during power tests

Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 crashes fairly often while running power usage tests.  I don't
  know what causes it, but I've collected a lot of data during the test
  runs and I hope someone will be able to make sense of the crash dumps
  and other logs.

  Here are some of the 162 instances I've seen so far...  inside each
  are numbered directories for each test run, and the crash dumps are
  inside of those under var-crash/ .

  Arale rc-proposed 61, runs 3 and 4:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_18:21:18-arale-61-power_usage_display_on/

  Arale devel-proposed 61, runs 1, 2, and 5:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

  Krillin rc-proposed 65, runs 2 and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/

  Krillin devel-proposed, runs 1 and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_22:02:04-krillin-132-power_usage_display_on/

  These are merely samples from recent test runs.  I've been seeing the
  crashes regularly ever since I started tracking crash dump files on
  July 3.

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

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

[Touch-packages] [Bug 1475547] [NEW] phone clock goes years into the future during power tests

[Selene Scriven]

Public bug reported:

This may be related to Bug 1475542, but instead of going to the past to
a hardcoded date before a test, the phone goes years into the future
during or after a test.

Again I'm not quite sure where to file this bug, but I've noticed that
the phone's time/date sometimes jump ahead to a fairly consistent range
of dates in the future while power tests are running.  This only happens
during/after a test, and even happens later in the same boot after I
force ntpdate to set the correct time.

On arale devices, the clock jumps to 2021-01-2X. On krillin devices, it
jumps to 2017-01-2X.  I've seen it happen 136 times, and only
during/after a test, never before.  So, the test forces the correct date
via ntpdate, disconnects to collect power measurements, then reconnects
to collect logs.  During this post-test log collection is when I see the
severely skewed date.

I see these date symptoms only during two tests...  the ones where wifi is 
turned off.
 89 power_usage_bt_on_wifi_disconnected
 47 power_usage_flight_mode_on

Power test logs are kept here: 
http://people.canonical.com/~platform-qa/power-results/?C=M;O=D
Each test set and test run there includes quite a bit of data and logs to help 
with debugging.

The specific recent test runs with this symptom are:
Arale tests:
2015-07-14_07:19:59-arale-56-power_usage_flight_mode_on/6
2015-07-14_08:39:52-arale-56-power_usage_bt_on_wifi_disconnected/3
2015-07-14_20:33:23-arale-58-power_usage_flight_mode_on/6
2015-07-15_03:33:10-arale-60-power_usage_bt_on_wifi_disconnected/2
2015-07-15_07:09:48-arale-59-power_usage_bt_on_wifi_disconnected/3
2015-07-15_12:12:39-arale-60-power_usage_flight_mode_on/3
2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/2
2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/3
2015-07-16_16:55:11-arale-60-power_usage_bt_on_wifi_disconnected/2
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/2
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/3
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/4
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/5
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/6
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/7

... and krillin tests:
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/2
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/4
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/5
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/6
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/1
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/2
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/3
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/4
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/5
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/6
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/7
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/2
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/3
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/6
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/7
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/1
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/2
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/3
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/4
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/6
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/7
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/8

Is there enough data in the logs there to identify the cause of this
issue? I can collect more logs or command output if necessary, to
include with future test runs.

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


** Tags: power-bugs

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

Title:
  phone clock goes years into the future during power tests

Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  This may be related to Bug 1475542, but instead of going to the past
  to a hardcoded date before a test, the phone goes years into the
  future during or after a test.

  Again I'm not quite sure where to file this bug, but I've noticed that
  the phone's time/date sometimes jump ahead to a fairly consistent
  range of dates in the future while power tests are running.  This only
  happens during/after a test, and even happens later in the same boot
  after I force ntpdate to set the correct time.

  On arale devices, the clock jumps to 2021-01-2X. On krillin devices,
  it jumps to 2017-01-2X.  I've seen it happen 

[Touch-packages] [Bug 1475523] Re: frequent unity8 crashes during power tests

[Selene Scriven]

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

The full channel and revision info is in each test run as channel.ini.

Thank you for finding the other bug for this; I didn't see it.  After
that bug is fixed, I can check results again to see if the symptoms of
this bug have stopped.

As for krillin, I don't normally have one hooked up to my power meter so
it doesn't get tested by me.  Max Brustkern runs the krillin tests, and
he may be able to provide more details there.  Or, when he gets the
results uploading automatically, the full logs should go to the same
base URL:

http://people.canonical.com/~platform-qa/power-results/?C=M;O=D

Max, can you answer comment 4?

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

Title:
  frequent unity8 crashes during power tests

Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 crashes fairly often while running power usage tests.  I don't
  know what causes it, but I've collected a lot of data during the test
  runs and I hope someone will be able to make sense of the crash dumps
  and other logs.

  Here are some of the 162 instances I've seen so far...  inside each
  are numbered directories for each test run, and the crash dumps are
  inside of those under var-crash/ .

  Arale rc-proposed 61, runs 3 and 4:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_18:21:18-arale-61-power_usage_display_on/

  Arale devel-proposed 61, runs 1, 2, and 5:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

  Krillin rc-proposed 65, runs 2 and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/

  Krillin devel-proposed, runs 1 and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_22:02:04-krillin-132-power_usage_display_on/

  These are merely samples from recent test runs.  I've been seeing the
  crashes regularly ever since I started tracking crash dump files on
  July 3.

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

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

[Touch-packages] [Bug 1475526] [NEW] unity8-dash crashes during power tests

[Selene Scriven]

Public bug reported:

Unity8-dash crashes fairly often while running power usage tests.  I
hope someone will be able to determine the root cause based on crash
dumps and other logs.

Here are some of the 170 instances I've seen so far... inside each are
numbered directories for each test run, and the crash dumps are inside
of those under var-crash/ .

Arale rc-proposed 61, runs 2, 3, and 4:
http://people.canonical.com/~platform-qa/power-results/2015-07-16_18:21:18-arale-61-power_usage_display_on/

Arale devel-proposed 61, runs 2, 5, and 8:
http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

Arale devel-proposed 60, runs 1, 2, 6, and 7:
http://people.canonical.com/~platform-qa/power-results/2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/

Krillin rc-proposed 62, runs 1, 3, 4, 5, 6, 7, and 8:
http://people.canonical.com/~platform-qa/power-results/2015-07-13_02:02:39-krillin-62-power_usage_idle/

Krillin devel-proposed 132, runs 1, 3, 6, and 7:
http://people.canonical.com/~platform-qa/power-results/2015-07-13_22:02:04-krillin-132-power_usage_display_on/

These are merely samples from recent test runs. I have plenty more if
you need them, or can add additional logging to get more data from
future tests.

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


** Tags: power-bugs

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

Title:
  unity8-dash crashes during power tests

Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8-dash crashes fairly often while running power usage tests.  I
  hope someone will be able to determine the root cause based on crash
  dumps and other logs.

  Here are some of the 170 instances I've seen so far... inside each are
  numbered directories for each test run, and the crash dumps are inside
  of those under var-crash/ .

  Arale rc-proposed 61, runs 2, 3, and 4:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_18:21:18-arale-61-power_usage_display_on/

  Arale devel-proposed 61, runs 2, 5, and 8:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

  Arale devel-proposed 60, runs 1, 2, 6, and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/

  Krillin rc-proposed 62, runs 1, 3, 4, 5, 6, 7, and 8:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_02:02:39-krillin-62-power_usage_idle/

  Krillin devel-proposed 132, runs 1, 3, 6, and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_22:02:04-krillin-132-power_usage_display_on/

  These are merely samples from recent test runs. I have plenty more if
  you need them, or can add additional logging to get more data from
  future tests.

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

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

[Touch-packages] [Bug 1475528] [NEW] maliit-server crashes during power tests

[Selene Scriven]

Public bug reported:

Maliit-server crashes fairly often while running power usage tests. I
hope someone will be able to determine the root cause based on crash
dumps and other logs.

Here are some of the 128 instances I've seen so far... inside each are
numbered directories for each test run, and the crash dumps are inside
of those under var-crash/ .

Arale rc-proposed 60, runs 3, 4, 5, and 7:
http://people.canonical.com/~platform-qa/power-results/2015-07-16_13:26:50-arale-60-power_usage_idle/

Arale devel-proposed 61, runs 2 and 3:
http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

Krillin rc-proposed 62, run 4:
http://people.canonical.com/~platform-qa/power-results/2015-07-13_03:46:40-krillin-62-power_usage_display_on/

Krillin rc-proposed 62, runs 4 and 5:
http://people.canonical.com/~platform-qa/power-results/2015-07-13_02:02:39-krillin-62-power_usage_idle/

These are merely samples from recent test runs. I have plenty more if
you need them, or can add additional logging to get more data from
future tests.

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


** Tags: power-bugs

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

Title:
  maliit-server crashes during power tests

Status in maliit-framework package in Ubuntu:
  New

Bug description:
  Maliit-server crashes fairly often while running power usage tests. I
  hope someone will be able to determine the root cause based on crash
  dumps and other logs.

  Here are some of the 128 instances I've seen so far... inside each are
  numbered directories for each test run, and the crash dumps are inside
  of those under var-crash/ .

  Arale rc-proposed 60, runs 3, 4, 5, and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_13:26:50-arale-60-power_usage_idle/

  Arale devel-proposed 61, runs 2 and 3:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

  Krillin rc-proposed 62, run 4:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_03:46:40-krillin-62-power_usage_display_on/

  Krillin rc-proposed 62, runs 4 and 5:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_02:02:39-krillin-62-power_usage_idle/

  These are merely samples from recent test runs. I have plenty more if
  you need them, or can add additional logging to get more data from
  future tests.

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

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

[Touch-packages] [Bug 1475542] [NEW] phone clock resets to Jan 1 2010 or 2014 during power tests

[Selene Scriven]

Public bug reported:

I'm not quite sure where to file this bug, but I've noticed that the
phone's time/date reset to what appear to be manufacturer defaults
sometimes while power tests are running  This even happens sometimes
after I force ntpdate to set the correct time.

On arale devices, the clock resets to 2010-01-01.  On krillin devices,
it resets to 2014-01-01.  I don't think the bug is hardware-specific,
but the symptoms are.

I've seen this symptom happen...
  - 3 times post-test on krillin
  - 12 times post-test on arale
  - 65 times pre-test on arale
  - 78 times pre-test on krillin

The tests generally do some setup (get online, install deps, configure
the device, force the correct date via ntpdate), disconnect USB, measure
performance for a while, reconnect, then collect additional logs and
data.  Most date-related errors are before the test runs, and are
corrected before proceeding, but it's especially interesting when it
happens during or after the test.

I see these date symptoms mostly during certain tests...
 89 power_usage_bt_on_wifi_disconnected
 52 power_usage_flight_mode_on
  2 power_usage_idle

Notably absent is the power_usage_display_on test, which suggests the
issue probably does not occur when the screen is on with wifi enabled.
It seems to happen during the tests where network access is turned off.

Power test logs are kept here:  
http://people.canonical.com/~platform-qa/power-results/?C=M;O=D
Each test set and test run there includes quite a bit of data and logs to help 
with debugging.

The specific recent test runs with this symptom are:
Arale tests:
2015-07-14_20:33:23-arale-58-power_usage_flight_mode_on/1
2015-07-14_20:33:23-arale-58-power_usage_flight_mode_on/5
2015-07-14_20:33:23-arale-58-power_usage_flight_mode_on/6
2015-07-14_20:33:23-arale-58-power_usage_flight_mode_on/7
2015-07-15_03:02:28-arale-60-power_usage_flight_mode_on/3
2015-07-15_03:33:10-arale-60-power_usage_bt_on_wifi_disconnected/2
2015-07-15_03:33:10-arale-60-power_usage_bt_on_wifi_disconnected/3
2015-07-15_03:33:10-arale-60-power_usage_bt_on_wifi_disconnected/4
2015-07-15_06:17:21-arale-59-power_usage_flight_mode_on/3
2015-07-15_07:09:48-arale-59-power_usage_bt_on_wifi_disconnected/2
2015-07-15_07:09:48-arale-59-power_usage_bt_on_wifi_disconnected/3
2015-07-15_07:09:48-arale-59-power_usage_bt_on_wifi_disconnected/4
2015-07-15_12:12:39-arale-60-power_usage_flight_mode_on/2
2015-07-15_12:12:39-arale-60-power_usage_flight_mode_on/3
2015-07-16_01:03:47-arale-60-power_usage_bt_on_wifi_disconnected/2
2015-07-16_01:03:47-arale-60-power_usage_bt_on_wifi_disconnected/3
2015-07-16_03:27:59-arale-61-power_usage_flight_mode_on/2
2015-07-16_13:26:50-arale-60-power_usage_idle/6
2015-07-16_13:26:50-arale-60-power_usage_idle/8
2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/2
2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/3
2015-07-16_16:55:11-arale-60-power_usage_bt_on_wifi_disconnected/2
2015-07-16_16:55:11-arale-60-power_usage_bt_on_wifi_disconnected/3
2015-07-16_16:55:11-arale-60-power_usage_bt_on_wifi_disconnected/4
2015-07-16_16:55:11-arale-60-power_usage_bt_on_wifi_disconnected/5
2015-07-16_19:32:27-arale-61-power_usage_bt_on_wifi_disconnected/2
2015-07-16_19:32:27-arale-61-power_usage_bt_on_wifi_disconnected/3
2015-07-16_19:32:27-arale-61-power_usage_bt_on_wifi_disconnected/4
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/2
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/3
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/4
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/5
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/6
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/7
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/8

... and some on krillin last time I tested one:
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/2
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/3
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/4
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/5
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/6
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/7
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/1
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/2
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/3
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/4
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/5
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/6
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/7
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/8
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/2
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/3
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/6

[Touch-packages] [Bug 1464466] [NEW] messaging-app SIM preference ignored for MMS

[Selene Scriven]

Public bug reported:

I discovered today that the user's choice of SIM slot (configured in the
messaging app) is only used for SMS.  This setting gets ignored for MMS,
and instead it uses whatever system settings / cellular has configured
for cell data.  This can cause failure to send MMS, if the other slot
has no service, or can cause the message to be sent from the wrong
number.

I saw this in krillin ubuntu-touch/ubuntu-rtm/14.09-factory-proposed
image 10, the OTA4 candidate.

I'm not sure how feasible it is to configure this in the same manner as
SMS uses, since the phone generally only connects to one cell data
provider at a time, but it would be nice if it used the same policies as
SMS.

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

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

Title:
  messaging-app SIM preference ignored for MMS

Status in messaging-app package in Ubuntu:
  New

Bug description:
  I discovered today that the user's choice of SIM slot (configured in
  the messaging app) is only used for SMS.  This setting gets ignored
  for MMS, and instead it uses whatever system settings / cellular has
  configured for cell data.  This can cause failure to send MMS, if the
  other slot has no service, or can cause the message to be sent from
  the wrong number.

  I saw this in krillin ubuntu-touch/ubuntu-rtm/14.09-factory-proposed
  image 10, the OTA4 candidate.

  I'm not sure how feasible it is to configure this in the same manner
  as SMS uses, since the phone generally only connects to one cell data
  provider at a time, but it would be nice if it used the same policies
  as SMS.

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

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

[Touch-packages] [Bug 1458936] Re: [arale] screen backlight remains on

[Selene Scriven]

On image 16, I consistently see the backlight turn off after 4 seconds,
not 30 to 60.

Version info:
 cat /tmp/channel.ini
[service]
base: sis.capomastro.canonical.com
http_port: 80
https_port: 443
channel: ubuntu-touch/rc-proposed/meizu
device: arale
build_number: 16
version_detail: device=20150526.34,custom=20150526.23,version=16

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

Title:
  [arale] screen backlight remains on

Status in the base for Ubuntu mobile products:
  Confirmed
Status in PowerD:
  In Progress
Status in powerd package in Ubuntu:
  New

Bug description:
  The screen backlight remains on after pressing the power button.

  ogra reported: on your arale device, flash image 15. Go to a dark
  place and press power and you'll notice that backlight stays on while
  the screen goes black. After 30sec to 1min backlight then turns off

  I can't reproduce it on mako with latest devel-proposed wily.

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

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

[Touch-packages] [Bug 1442851] Re: [browser] Setting labels ellipsized on phone screen in portrait orientation

[Selene Scriven]

I see this partially fixed in a silo.  One item still ends in an
ellipsis.  Shouldn't this be fixed at a toolkit level instead of just
shortening the labels?  Otherwise it'll still fail when translated to a
longer string or when run on a different screen size or with a different
font size.

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

Title:
  [browser] Setting labels ellipsized on phone screen in portrait
  orientation

Status in Ubuntu UX bugs:
  Triaged
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in webbrowser-app source package in Vivid:
  New

Bug description:
  As shown on the attached screenshot, the rows #2 and #3 of the settings 
screen have a text that doesn't fit on the screen.
  The only way to see what these options mean is to switch the phone to 
landscape orientation.

  A different UI component should be used for these two options, one
  that allows the user to see the full text of what he's enabling or
  disabling.

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

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

[Touch-packages] [Bug 1442851] Re: [browser] Setting labels ellipsized on phone screen in portrait orientation

[Selene Scriven]

** Attachment added: half-fixed.png
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1442851/+attachment/4398324/+files/half-fixed.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/1442851

Title:
  [browser] Setting labels ellipsized on phone screen in portrait
  orientation

Status in Ubuntu UX bugs:
  Triaged
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in webbrowser-app source package in Vivid:
  New

Bug description:
  As shown on the attached screenshot, the rows #2 and #3 of the settings 
screen have a text that doesn't fit on the screen.
  The only way to see what these options mean is to switch the phone to 
landscape orientation.

  A different UI component should be used for these two options, one
  that allows the user to see the full text of what he's enabling or
  disabling.

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

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

[Touch-packages] [Bug 1453289] [NEW] network-manager asks for passwords it already knows

[Selene Scriven]

Public bug reported:

Sometimes Network Manager (and the network indicator) asks for passwords
it already knows.  This issue is intermittent and I'm not yet sure what
causes it, but it has been happening for a long time on many different
devices.

I'm seeing it happen in Ubuntu Touch on krillin, but also on every other
Ubuntu Touch device I've ever used and every notebook I've ever tried
Network Manager on.  This bug is specifically targeting Ubuntu Touch
though.

The issue is easiest to trigger by rebooting the phone.  While
developing a new reboot loop test, I saw this happen on 8 of 12 boots
during a short test sequence.  The logs from that are attached, though
I'm not sure if it contains nearly enough information.

Triggering the issue is sometimes difficult due to the intermittent
nature, but in general it usually happens if I leave a device idle
overnight.  In the morning I'm greeted by a dialog asking for my wifi
password.  If I cancel the dialog it will connect successfully (though
sometimes I also have to drag down the indicator and tap the network to
tell it to connect), so it hasn't forgotten the password.

If more logs are needed, let me know which ones and I can add them to
the test.

** Affects: indicator-network (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Attachment added: reboot-test-nm-password-dialog.tar.bz2
   
https://bugs.launchpad.net/bugs/1453289/+attachment/4393861/+files/reboot-test-nm-password-dialog.tar.bz2

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

Title:
  network-manager asks for passwords it already knows

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Network Manager (and the network indicator) asks for
  passwords it already knows.  This issue is intermittent and I'm not
  yet sure what causes it, but it has been happening for a long time on
  many different devices.

  I'm seeing it happen in Ubuntu Touch on krillin, but also on every
  other Ubuntu Touch device I've ever used and every notebook I've ever
  tried Network Manager on.  This bug is specifically targeting Ubuntu
  Touch though.

  The issue is easiest to trigger by rebooting the phone.  While
  developing a new reboot loop test, I saw this happen on 8 of 12 boots
  during a short test sequence.  The logs from that are attached, though
  I'm not sure if it contains nearly enough information.

  Triggering the issue is sometimes difficult due to the intermittent
  nature, but in general it usually happens if I leave a device idle
  overnight.  In the morning I'm greeted by a dialog asking for my wifi
  password.  If I cancel the dialog it will connect successfully (though
  sometimes I also have to drag down the indicator and tap the network
  to tell it to connect), so it hasn't forgotten the password.

  If more logs are needed, let me know which ones and I can add them to
  the test.

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

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

[Touch-packages] [Bug 1453289] Re: network-manager asks for passwords it already knows

[Selene Scriven]

** Description changed:

  Sometimes Network Manager (and the network indicator) asks for passwords
  it already knows.  This issue is intermittent and I'm not yet sure what
  causes it, but it has been happening for a long time on many different
  devices.
  
- I'm seeing it happen in Ubuntu Touch on krillin, but also on every other
- Ubuntu Touch device I've ever used and every notebook I've ever tried
- Network Manager on.  This bug is specifically targeting Ubuntu Touch
- though.
+ I'm seeing it happen in Ubuntu Touch on krillin (rtm 274, OTA3.5
+ candidate), but also on every other Ubuntu Touch device I've ever used
+ and every notebook I've ever tried Network Manager on.  This bug is
+ specifically targeting Ubuntu Touch though.
  
  The issue is easiest to trigger by rebooting the phone.  While
  developing a new reboot loop test, I saw this happen on 8 of 12 boots
  during a short test sequence.  The logs from that are attached, though
  I'm not sure if it contains nearly enough information.
  
  Triggering the issue is sometimes difficult due to the intermittent
  nature, but in general it usually happens if I leave a device idle
  overnight.  In the morning I'm greeted by a dialog asking for my wifi
  password.  If I cancel the dialog it will connect successfully (though
  sometimes I also have to drag down the indicator and tap the network to
  tell it to connect), so it hasn't forgotten the password.
  
  If more logs are needed, let me know which ones and I can add them to
  the test.

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

Title:
  network-manager asks for passwords it already knows

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Network Manager (and the network indicator) asks for
  passwords it already knows.  This issue is intermittent and I'm not
  yet sure what causes it, but it has been happening for a long time on
  many different devices.

  I'm seeing it happen in Ubuntu Touch on krillin (rtm 274, OTA3.5
  candidate), but also on every other Ubuntu Touch device I've ever used
  and every notebook I've ever tried Network Manager on.  This bug is
  specifically targeting Ubuntu Touch though.

  The issue is easiest to trigger by rebooting the phone.  While
  developing a new reboot loop test, I saw this happen on 8 of 12 boots
  during a short test sequence.  The logs from that are attached, though
  I'm not sure if it contains nearly enough information.

  Triggering the issue is sometimes difficult due to the intermittent
  nature, but in general it usually happens if I leave a device idle
  overnight.  In the morning I'm greeted by a dialog asking for my wifi
  password.  If I cancel the dialog it will connect successfully (though
  sometimes I also have to drag down the indicator and tap the network
  to tell it to connect), so it hasn't forgotten the password.

  If more logs are needed, let me know which ones and I can add them to
  the test.

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

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

[Touch-packages] [Bug 1452300] Re: Reboot takes too long

[Selene Scriven]

** Description changed:

  Test case.
- - Without usb cable connected
+ - Make sure phone is not plugged in.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.
  
  Expected result.
  - Must take similar time than stable.
  
  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.
  
  syslog:
  
  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=816 x-info=http://w
  ww.rsyslog.com] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=817 x-info=http://w
  ww.rsyslog.com] start
  
  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

Title:
  Reboot takes too long

Status in the base for Ubuntu mobile products:
  New
Status in powerd package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in powerd source package in Vivid:
  New
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  Test case.
  - Make sure phone is not plugged in.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=816 x-info=http://w
  ww.rsyslog.com] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=817 x-info=http://w
  ww.rsyslog.com] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

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

[Touch-packages] [Bug 1452300] Re: Reboot takes too long

[Selene Scriven]

Fixed the test steps; phone must not be connected via USB.

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

Title:
  Reboot takes too long

Status in the base for Ubuntu mobile products:
  New
Status in powerd package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in powerd source package in Vivid:
  New
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  Test case.
  - Make sure phone is not plugged in.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=816 x-info=http://w
  ww.rsyslog.com] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd 
swVersion=7.4.4 x-pid=817 x-info=http://w
  ww.rsyslog.com] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

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

[Touch-packages] [Bug 1411722] Re: [webapps-container] Add proper support for multiple windows

[Selene Scriven]

This is good in that it adds the ability to open third-party sites
without falling back to the core browser app, but it's a bit awkward
since it uses a mechanism totally different than how the browser handles
it.  Multiple tabs might be nicer, so that the user could switch back
and forth between the original app and the site(s) they opened.  I tend
to use the primary browser instead of site-specific webapps because it
gives me regular tab and browser functions instead of the more limited
functionality in webapps.

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

Title:
  [webapps-container] Add proper support for multiple windows

Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Add proper support for external window requests triggered from the
  browsing session in the container in cases such as:

  - window.open,
  - a href w/ blank target,

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

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

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

[Selene Scriven]

Fixed in silo ubuntu/landing-006 today for vivid.  At least, the
checkbox stays in one state and won't respond or change until the
transition is complete, which seems acceptable.

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

Title:
  need a transition state for indicators reflecting laggy backends

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

Bug description:
  spawned from efforts in bug 1336715

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

  comment from dizzypaty

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

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

  
  Desired resolution

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1427064] Re: Wi-Fi indicator icon does not update when the connected AP's strength changes

[Selene Scriven]

Fixed in silo ubuntu/landing-006 today for vivid.

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

Title:
  Wi-Fi indicator icon does not update when the connected AP's strength
  changes

Status in indicator-network package in Ubuntu:
  New
Status in indicator-network package in Ubuntu RTM:
  Fix Released

Bug description:
  The top panel Wi-Fi icon always indicates the signal strength of the
  connected AP at the time of connecting to it. Changes to the signal
  strength of the connected AP should update this icon.

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

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

[Touch-packages] [Bug 1436630] [NEW] must unlock screen even if it was only off for a few seconds

[Selene Scriven]

Public bug reported:

On Ubuntu Touch so far (vivid, mid-March 2015), it is still necessary to
unlock the screen after it shuts off, even if the screen was only off
for a few seconds.  This is inconvenient, and it would be much easier if
the lock didn't activate for ~10 seconds after the screen turns itself
off.

If the user activates the screen-off event by tapping the power button,
then it's okay to lock immediately.  If the screen times out though, it
should probably delay before locking, to give the user a chance to turn
the screen back on.

Could we add a ~10 second delay between automatic screen shutoff and
screen lock?

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

Title:
  must unlock screen even if it was only off for a few seconds

Status in unity8 package in Ubuntu:
  New

Bug description:
  On Ubuntu Touch so far (vivid, mid-March 2015), it is still necessary
  to unlock the screen after it shuts off, even if the screen was only
  off for a few seconds.  This is inconvenient, and it would be much
  easier if the lock didn't activate for ~10 seconds after the screen
  turns itself off.

  If the user activates the screen-off event by tapping the power
  button, then it's okay to lock immediately.  If the screen times out
  though, it should probably delay before locking, to give the user a
  chance to turn the screen back on.

  Could we add a ~10 second delay between automatic screen shutoff and
  screen lock?

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

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

[Touch-packages] [Bug 1436018] Re: No sound for incoming calls

[Selene Scriven]

I can confirm this happens on vivid image 159 on krillin.  The first
call played a ring tone, but every call after that vibrated with no
sound.

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

Title:
  No sound for incoming calls

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  vivid-proposed image 158, krillin

  1. Call your Ubuntu phone from another device and make sure ringtone plays
  2. Reject the call from Ubuntu phone
  3. repeat step 1 and 2

  On third retry there is no sound played for the incoming call, only
  the vibration

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150227-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: armhf
  Date: Tue Mar 24 23:57:01 2015
  InstallationDate: Installed on 2015-03-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150324-020203)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1436013] Re: No notification for incoming call

[Selene Scriven]

I've been trying to trigger this issue and haven't been able to.  The
incoming call dialog shows every time and it vibrates every time, though
sometimes it takes up to 15 seconds to happen.

However, I consistently see a related issue where the messaging
indicator shows fewer missed calls than there should be.

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

Title:
  No notification for incoming call

Status in unity8 package in Ubuntu:
  New

Bug description:
  krillin image 158

  After rejecting an incoming call multiple times, the incoming call
  notification stops appearing.

  1. Dial your Ubuntu phone from another phone
  2. Reject call from Ubuntu phone
  3. repeat step 1 and 2 multiple times

  What happens:
  No notification for incoming call, no sound whatsoever.

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

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

[Touch-packages] [Bug 1350958] Re: flash option should be disabled when selecting HDR

[Selene Scriven]

FWIW, this fix breaks a use case which worked before.  It is no longer
possible to use the flash to help the camera focus the image before
taking an HDR pic.

Pre-image focus light should probably be its own option instead of being
entagled in the during-exposure flash setting, but I thought I should at
least mention it because HDR pics end up being lower-quality after
applying this fix.

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

Title:
  flash option should be disabled when selecting HDR

Status in Camera App:
  In Progress
Status in the base for Ubuntu mobile products:
  New
Status in camera-app package in Ubuntu:
  Fix Released
Status in camera-app package in Ubuntu RTM:
  New

Bug description:
  HDR and Flash are mutually exlusive. If one is on the other has to be
  off. Currently you can enable both and it's confusing to the user that
  the flash won't work if HDR is on. We should update the UI to reflect
  that flash turns off when HDR is on.

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

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

[Touch-packages] [Bug 1350958] Re: flash option should be disabled when selecting HDR

[Selene Scriven]

The HDR+flash mode pre-flash also helped with red-eye reduction, by
constricting pupils.

So, it's nice that the UI reflects that the flash won't be enabled
during exposure, but as a side effect it also breaks the most reliable
method of getting good-quality indoor photos.  The pre-flash helps with
focus and red-eye, while HDR with no flash gets the best color.  With
the flash fully off it's harder to focus, and with the flash fully on
the colors and lighting get weird.

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

Title:
  flash option should be disabled when selecting HDR

Status in Camera App:
  In Progress
Status in the base for Ubuntu mobile products:
  New
Status in camera-app package in Ubuntu:
  Fix Released
Status in camera-app package in Ubuntu RTM:
  New

Bug description:
  HDR and Flash are mutually exlusive. If one is on the other has to be
  off. Currently you can enable both and it's confusing to the user that
  the flash won't work if HDR is on. We should update the UI to reflect
  that flash turns off when HDR is on.

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

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

[Touch-packages] [Bug 1422328] Re: Allow users to create their own aggregator scopes without programming

[Selene Scriven]

FWIW, this functionality is covered in Android by using widgets.  Users
can arrange arbitrary widgets freely in several Android launchers, such
as ADWLauncher.  Each app can provide multiple widgets for different
styles and functions, to make that app's data and operations usable
directly from the launcher screens without having to actually launch the
app... and the user can easily group or arrange them however they like
with a few taps and gestures.

Just as a point of reference for what people may be expecting as
baseline functionality.

If anyone in design would like a demo, I have a friend in London who
loves Ubuntu and would be happy to show how this UI works along with
several other useful concepts.  I'd also love to see more end-user-
configurable scopes.

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

Title:
  Allow users to create their own aggregator scopes without programming

Status in Ubuntu UX bugs:
  New
Status in unity-scope-scopes package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity-scope-scopes package in Ubuntu RTM:
  New
Status in unity-scopes-shell package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  It would be nice if there were an UI to create your own (virtual)
  aggregator scopes straight from the Unity8 dash without any
  programming efforts. They would then display data from a few scopes
  which the user would be able to select from the ones he has installed
  using a layout the user would be able to define as well. Then there
  would be a new page in the Unity8 dash which collocates the data in
  the way the user wanted to.

  Here's a usage scenario outlining why I think this functionality is
  important:

  Let's say you read news from 4 custom news sources regularly for which
  scopes do exist. Currently, you then need to favorite all of them
  separately, resulting in the addition of 4 pages to the dash. As a
  result, you will have to swipe a lot to reach the scopes you want,
  which is quite annoying.

  Now imagine you need to do the same for other types of content and you
  will have a notion of how crowded your dash will become. To keep it
  short, the user experience will be suboptimal.

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

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

[Touch-packages] [Bug 1420528] [NEW] click scope search is sometimes case sensitive

[Selene Scriven]

Public bug reported:

I found a great new feature in the click scope search function today.  I
can search for price:2.99 to find paid apps!  Woot!

Unfortunately, searching for Price:2.99 does not work.  The prefix
appears to be case-sensitive.  And auto-caps are how the OSK enters text
by default.

Could we remove the case sensitivity here?

This was on krillin rtm 232.

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

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

Title:
  click scope search is sometimes case sensitive

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  I found a great new feature in the click scope search function today.
  I can search for price:2.99 to find paid apps!  Woot!

  Unfortunately, searching for Price:2.99 does not work.  The prefix
  appears to be case-sensitive.  And auto-caps are how the OSK enters
  text by default.

  Could we remove the case sensitivity here?

  This was on krillin rtm 232.

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

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

[Touch-packages] [Bug 1389510] Re: SD card and contents listed several times

[Selene Scriven]

Drat, I just noticed the logs never got attached.  My notebook has been
awfully crashy lately too, and I don't have the files any more.  Will
have to get these logs during the next sanity test run.

I think the snippet from earlier is at least enough to show the issue is
phone-side though, and not client-side.

** Changed in: mtp (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  SD card and contents listed several times

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  When connecting to a krillin running rtm image 142, I see the SD card
  device listed several times.  If I connect to that device and list its
  contents, each file and directory is listed several times too.  The
  exact number is consistent during a session, but varies per boot.

  If I then add a new file, disconnect, and reconnect, that file is
  listed just once while everything else is listed several times.

  The mtp client I'm using to test this is gmtp.  Results may appear
  different with Nautilus, because I think it ignores duplicates.

  Screenshots demonstrating what I see are attached.

  This issue isn't new, but it seems to happen every time now instead of
  just once in a while.

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

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

[Touch-packages] [Bug 1414560] Re: Parent scope is authorised when logging in to a child scope

[Selene Scriven]

This does improve the behavior, but it still has bugs.

Both the parent scope and child scope get authorized. This is fine, but
the user cannot then change it so that only one scope or the other has
access.  The settings UI will allow just the one scope to be selected,
but it saves the change to both.  And it takes a few taps before it'll
visually allow just one; at first, both checkboxes change in sync.

So, it's better than it was... but still needs further improvements.

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

Title:
  Parent scope is authorised when logging in to a child scope

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu RTM:
  In Progress
Status in unity-scopes-shell package in Ubuntu RTM:
  In Progress

Bug description:
  When logging into a child scope from an aggregator, the parent scope
  is added to the ACL instead of the child scope. The aggregator should
  request authentication on behalf of the child scope in these cases.

  To reproduce the bug:
    1. Ensure that signon-apparmor-extension is installed on the phone: sudo 
apt-get install signon-apparmor-extension
    2. Log into Facebook Photos from the Photos scope. (Tap No Facebook Photos 
account configured)

  What should happen:
  Once focus is returned to the Photos scope, the scope should refresh, now 
displaying your personal Facebook photos.

  What actually happens:
  Focus returns to the Photos scope and nothing happens. Neither the Photos 
scope nor the Facebook Photos scope show your personal Facebook pictures, yet 
settings indicates the scopes are authenticated.

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

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

[Touch-packages] [Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app

[Selene Scriven]

It's great that users can now disable access...  but I see two other
issues now:

- After disabling access to an app, the app is still shown as being
allowed to access location services.  Just exit the settings app and re-
start it, and the UI shows access as enabled again.

- After disabling access to an app, the user cannot re-enable access.
It's shown as enabled, but it no longer works.  Toggling the checkbox no
longer seems to do anything.

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

Title:
  Location service uses the cached authorization, even if the user
  denied location access to an app

Status in the base for Ubuntu mobile products:
  In Progress
Status in trust-store:
  In Progress
Status in location-service package in Ubuntu:
  Invalid
Status in trust-store package in Ubuntu:
  Fix Released
Status in location-service source package in Utopic:
  Invalid
Status in trust-store source package in Utopic:
  In Progress
Status in location-service source package in Vivid:
  Invalid
Status in trust-store source package in Vivid:
  Fix Released
Status in trust-store package in Ubuntu RTM:
  In Progress

Bug description:
  The bug occurs after removing location access authorization to an
  application. The location is still available to the application,
  despite the user having revoked access from within USS  Privacy 
  Location.

  To reproduce:

  1. Open a map application, like Here map
  2. Allow access to location
  3. Switch to System Settings  Privacy  Location
  4. Disable location access for Maps
  5. Kill Here map, and restart it

  What should happen: you should not have access anymore (and should not see a 
prompt)
  What happens instead: the app still has access to your location, as shown in 
the logs:

  I1030 16:15:38.167752  3100 cached_agent_glog_reporter.cpp:32]
  CachedAgent::authenticate_request_with_parameters: Application pid:
  27975 Application uid: 32011 Application id:  com.nokia.heremaps_here
  Cached request:   Request(from: com.nokia.heremaps_here, feature: 0,
  when: 1414682114882519283, answer: granted)

  I confirmed that the trust store had recorded the authorization change
  as in:

  phablet@ubuntu-phablet:~$ sqlite3 
~/.local/share/UbuntuLocationService/trust.db select * from requests
  1|unconfined|0|1414098093331252474|1
  2|com.nokia.heremaps_here|0|1414682114882519283|1
  3|com.nokia.heremaps_here|0|1414682131206341515|0

  From a user's perspective: Despite having explicitly rejected trust to
  an application, the app would still be able to access services.

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

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

[Touch-packages] [Bug 1396985] Re: Dbus-c++ leaks memory

[Selene Scriven]

Having trouble testing this in place on the phone.  Any hints on what
process(es) to measure or how to make it leak?  I didn't see any memory
increase in any of the processes I checked.

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

Title:
  Dbus-c++ leaks memory

Status in the base for Ubuntu mobile products:
  In Progress
Status in DBus C++:
  In Progress
Status in dbus-cpp package in Ubuntu:
  Fix Released

Bug description:
  The sample program that comes with dbus-cpp (and thus presumably all
  clients of dbus-cpp) leaks memory quite badly. To test do this:

  valgrind --tool=massif --trace-children=yes
  examples/benchmark/benchmark

  Then view the result with massif-viewer. The image is attached and
  shows that memory consumption keeps on increasing all the time and
  never drops. Presumably because dbus-cpp is not properly releasing
  resources in libdbus-1.

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

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

[Touch-packages] [Bug 1411323] Re: [address book] share handler screen has a confusing ok icon

[Selene Scriven]

This is certainly better than it was before, but it's still a little
confusing.  Now the icons are X on the left, and two checkmarks on the
right (one in a box, one without a box).  The difference between the two
checkmarks isn't particularly obvious based only on appearance.

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

Title:
  [address book] share handler screen has a confusing ok icon

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

Bug description:
  as found on user testing, the share icon is confusing for users that
  get to this screen and do not know how to proceed.

  Steps to reproduce:
  Using telegram
  click in contacts
  then click  in import
  select from address book
  once the content hub launches, select the address book
  select a few contact

  Expected result:
  there is a clear button to ok selection, that matches the X to cancel. 
Maybe a tick like in the camera app

  Actual result:
  A share icon is used to ok

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

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

[Touch-packages] [Bug 1403464] Re: Left-edge / home does not close Manage Dash

[Selene Scriven]

This fix does what it says, but it isn't reversible.  As soon as the
first commit point is reached, the scope management screen goes away and
cannot be retrieved by sliding back the other direction.

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

Title:
   Left-edge / home does not close Manage Dash

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  In Progress

Bug description:
  The Manage Dash should be closed on  Left-edge / home press

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

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