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

[Ricardo Salveti]

Adding task for indicator-sound again as the new UX spec requires
changes for the indicator as well.

** Changed in: indicator-sound (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Make music controls work in the sound indicator

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

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

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

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

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

[Dx-packages] [Bug 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible

[Ricardo Salveti]

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1442166

Title:
  Calendar alarms rings forever if Low Battery dialog visible

Status in the base for Ubuntu mobile products:
  In Progress
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  I'm on rtm build 258 on krillin

  Steps to reproduce:
  - let battery run down on phone (was sitting unplugged for 1 or 2 days)
  - in the morning, a calendar alarm starting ringing/vibrating and would not 
stop
  - when I looked at the phone, the screen was on and I see the Low Battery 
dialog
  - after dismissing the dialog, then I see the notification for the alarm, and 
only after 5-10 more seconds does the ringing stop

  Seems like while the Low Battery dialog is displayed it keeps the
  alarm ringing forever

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

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

[Dx-packages] [Bug 1446703] Re: Receiving a USSD while phone on mute shows sound OSD

[Ricardo Salveti]

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1446703

Title:
  Receiving a USSD while phone on mute shows sound OSD

Status in the base for Ubuntu mobile products:
  In Progress
Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin

  Steps to reproduce:
   * set sound on phone to minimum (mute)
   * perform an action that results in delivery of a USSD (e.g. request some 
info from the operator - I get a USSD from giffgaff giving balance info after 
sending a SMS for example)

  Expected result:
   - get the USSD pop up with no audible notification

  Actual result:
   - get the USSD and the sound OSD pops up show sound level

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

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

[Dx-packages] [Bug 1446703] Re: Receiving a USSD while phone on mute shows sound OSD

[Ricardo Salveti]

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1446703

Title:
  Receiving a USSD while phone on mute shows sound OSD

Status in the base for Ubuntu mobile products:
  New
Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin

  Steps to reproduce:
   * set sound on phone to minimum (mute)
   * perform an action that results in delivery of a USSD (e.g. request some 
info from the operator - I get a USSD from giffgaff giving balance info after 
sending a SMS for example)

  Expected result:
   - get the USSD pop up with no audible notification

  Actual result:
   - get the USSD and the sound OSD pops up show sound level

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

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

[Dx-packages] [Bug 1443178] [NEW] Accounts Service always relies on language fallback if never set by the user

[Ricardo Salveti]

Public bug reported:

current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412

This causes a bad side effect when changing volume via indicator-sound,
as that will cause a sync to accountsservice in order to sync the
volume. Once that sync happens, it will request the user properties, and
in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).

As a test, just flash latest vivid image on mako, don't set any language
when the wizard shows up, run top and then change the volume by pressing
volume up/down. This is what I see with mako:

 PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
2609 phablet   20   0  499660 121220  52688 S   7.6  6.5   0:41.69 unity8
5600 phablet   20   03676   1760   1288 R   6.0  0.1   0:00.19 
language-option
1312 root  20   0  211532  15572  11344 S   1.9  0.8   0:07.25 
unity-system-co
1316 phablet   20   0   36532   3792   2928 S   1.3  0.2   0:01.66 
accounts-daemon

And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
   guint   param_id,
   GValue *value,
   GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else 
g_value_set_string (value, user_get_fallback_value 
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_string (value, user->formats_locale);
else 
g_value_set_string (value, user_get_fallback_value 
(user, "FormatsLocale"));
break;

user_set_property never gets called unless the user changes the system
language from system-settings or wizard.

Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/, causing this behavior to stop.

Another bad side effect of this issue is that it takes quite a while for
accountsservice to reply back to indicator-sound when the sync happens,
possibly causing sync aborts (as indicator-sound only waits 1 second
before triggering another sync).

Some possible ways to fix this issue:
1) Make wizard to set language even when the selected language is already the 
default one;
2) Change accountsservice to save the fallback value at the first time it gets 
that from the system;

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

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

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

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1443178

Title:
  Accounts Service always relies on language fallback if never set by
  the user

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

Bug description:
  current build number: 169
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-12 20:38:14
  version version: 169
  version ubuntu: 20150412
  version device: 20150210
  version custom: 20150412

  This causes a bad side effect when changing volume via indicator-
  sound, as that will cause a sync to accountsservice in order to sync
  the volume. Once that sync happens, it will request the user
  properties, and in case the user doesn't have a valid language at
  /var/lib/AccountsService/users/, it will always rely on the
  fallback, which would be fine if calculating the fallback wasn't 't so
  cpu or i/o intensive (and that happens multiple times).

  As a test, just flash latest vivid image on mako, don't set any
  language when the wizard shows up, run top and then change the volume
  by pressing volume up/down. This is what I see with mako:

   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  2609 phablet   20   0  499660 121220  52688 S   7.6  6.5   0:41.69 unity8
  5600 phablet   20   03676   1760   1288 R   6.0  0.1   0:00.19 
language-option
  1312 root  20   0  211532  15572  11344 S   1.9  0.8   0:07.25 
unity-system-co
  1316 phab

[Dx-packages] [Bug 1443005] [NEW] Indicator shouldn't set volume on pulse/account service if the volume didn't change

[Ricardo Salveti]

Public bug reported:

current build number: 168
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 03:49:09
version version: 168
version ubuntu: 20150411
version device: 20150210
version custom: 20150411

This is a regression from RTM.

The current logic doesn't check for the volume value before calling
pulseaudio and account service when updating the volume variable. The
consequence is that it will set the volume at least twice after you
change it, since it will get a callback from account service, and that
will result in another volume set with the exact same volume.

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1443005

Title:
  Indicator shouldn't set volume on pulse/account service if the volume
  didn't change

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  current build number: 168
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-12 03:49:09
  version version: 168
  version ubuntu: 20150411
  version device: 20150210
  version custom: 20150411

  This is a regression from RTM.

  The current logic doesn't check for the volume value before calling
  pulseaudio and account service when updating the volume variable. The
  consequence is that it will set the volume at least twice after you
  change it, since it will get a callback from account service, and that
  will result in another volume set with the exact same volume.

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

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

[Dx-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness

[Ricardo Salveti]

Device tarball was validated by QA already, waiting for John to publish
it.

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

Title:
  brigtness slider should not allow total darkness

Status in the base for Ubuntu mobile products:
  In Progress
Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  bq aquaris 4.5, Utopic Unicorn 20150312-002053:
  slider allows to minimize the brightess to the point of not seeing at all.
  Even if you manage to reboot (you don't see the confirmation dialogue) you 
still have completly dark display which effectively "bricks" the phone (no 
battery removal) unless you are patient enought to blindly try and hit long 
time enough to increase the brigtness again.

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

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

[Dx-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness

[Ricardo Salveti]

I proposed a change to change minimum from 5 to 10, which should cover
your issue specifically.

If you want a workaround until next OTA is out (1-2 weeks), do the following 
(from your host):
1 - Download the attached config file and save as config-krillin.xml
2 - adb push config-krillin.xml /tmp/
3 - adb shell:
$ sudo mount -o remount,rw /
$ sudo cp /tmp/config-krillin.xml 
/usr/share/powerd/device_configs/config-krillin.xml
$ sudo reboot

Also opened bug 1437510 for the dim issue, as that is indeed a problem.

** Attachment added: "config-krillin.xml"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1436538/+attachment/4358308/+files/config-krillin.xml

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

Title:
  brigtness slider should not allow total darkness

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  bq aquaris 4.5, Utopic Unicorn 20150312-002053:
  slider allows to minimize the brightess to the point of not seeing at all.
  Even if you manage to reboot (you don't see the confirmation dialogue) you 
still have completly dark display which effectively "bricks" the phone (no 
battery removal) unless you are patient enought to blindly try and hit long 
time enough to increase the brigtness again.

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

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

[Dx-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness

[Ricardo Salveti]

That's weird as I can't reproduce this with my device, but I'm still
using a prototype.

Asking someone with a final device to give another try, but we can for
sure try to change the minimal value as required.

You can restore back the brightness if you have access to a terminal, by doing 
the following:
sudo echo 10 > /sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightness

Can you play with the values and find out what is the minimum you get
that is still able to see visualize unity8? Our minimum is currently 5,
so would be great if you could play with that bit and give us the
feedback.

Thanks

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

Title:
  brigtness slider should not allow total darkness

Status in indicator-power package in Ubuntu:
  New

Bug description:
  bq aquaris 4.5, Utopic Unicorn 20150312-002053:
  slider allows to minimize the brightess to the point of not seeing at all.
  Even if you manage to reboot (you don't see the confirmation dialogue) you 
still have completly dark display which effectively "bricks" the phone (no 
battery removal) unless you are patient enought to blindly try and hit long 
time enough to increase the brigtness again.

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

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

[Dx-packages] [Bug 1436971] Re: calendar alarm would not stop sounding

[Ricardo Salveti]

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

** This bug has been marked a duplicate of bug 1436162
   [pulsesink] abort at pthread_mutex_unlock(&m->mutex) == 0' failed at 
pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1436971

Title:
  calendar alarm would not stop sounding

Status in indicator-datetime package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  vivid-proposed on mako

  I had a calendar alarm notification sound at 9:00am this morning and
  it keep ringing/vibrating and did not go away until I swiped it. At
  that point, I think something crashed because my datetime indicator is
  stuck at 9:01am and I cannot launch Time and Date settings from the
  menu.

  I do have a crash file (with an earlier timestamp, so not sure if it's
  the same or different crash). Attaching that and the indicator-
  datetime log files

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

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

[Dx-packages] [Bug 1435736] Re: alarms and event notifications causes time to freeze

[Ricardo Salveti]

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

** This bug is no longer a duplicate of bug 1435867
   cannot play next or previous song in music player
** This bug has been marked a duplicate of bug 1436162
   [pulsesink] abort at pthread_mutex_unlock(&m->mutex) == 0' failed at 
pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1435736

Title:
  alarms and event notifications causes time to freeze

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On latest vivid, snoozing an alarm causes the time in the indicator to
  freeze. Here's a screenshot of the phone after I snoozed an alarm
  today morning at 9am.

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

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

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

[Ricardo Salveti]

Our hope is for this to land between week 17-19, as it depends on
background playlist support, which is currently in our sprint backlog.

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

Title:
  Make music controls work in the sound indicator

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

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

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

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

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

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

[Ricardo Salveti]

On Thu, Mar 19, 2015 at 7:17 PM, Jim Hodapp <1378...@bugs.launchpad.net> wrote:
> Plan is to work on underlying background playlist support this next
> iteration, so this will be possible to re-enable in the next few weeks
> or so.

Right, can only land once the background playlist support is fully
implemented (too big for 14.09/RTM OTA).

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

Title:
  Make music controls work in the sound indicator

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

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

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

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

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

[Dx-packages] [Bug 1425297] Re: Sometimes indicator-datetime is not available in the UI after a reboot (vivid/mako)

[Ricardo Salveti]

Also happens with RTM.

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

** Summary changed:

- Sometimes indicator-datetime is not available in the UI after a reboot 
(vivid/mako)
+ Sometimes indicator-datetime is not available in the UI after a reboot

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1425297

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

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

[Dx-packages] [Bug 1425297] Re: Sometimes indicator-datetime is not available in the UI when rebooting vivid/mako 110

[Ricardo Salveti]

Was also able to reproduce this with krillin.

** Summary changed:

- Sometimes indicator-datetime is not available in the UI when rebooting 
vivid/mako 110
+ Sometimes indicator-datetime is not available in the UI after a reboot 
(vivid/mako 110)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1425297

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot
  (vivid/mako 110)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

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

[Dx-packages] [Bug 1425297] [NEW] Sometimes indicator-datetime is not available in the UI after a reboot (vivid/mako 110)

[Ricardo Salveti]

Public bug reported:

current build number: 110
device name: mako
channel: ubuntu-touch/vivid-proposed
last update: 2015-02-24 04:34:45
version version: 110
version ubuntu: 20150224
version device: 20150210
version custom: 20150224

See the attached picture.

The only log entry I have for it:
Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

** Attachment added: "missing-indicator-datetime.jpg"
   
https://bugs.launchpad.net/bugs/1425297/+attachment/4326711/+files/missing-indicator-datetime.jpg

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1425297

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot
  (vivid/mako 110)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

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

[Dx-packages] [Bug 1425297] Re: Sometimes indicator-datetime is not available in the UI after a reboot (vivid/mako 110)

[Ricardo Salveti]

The process was active and running, just not showing in the UI. After
killing the service it worked fine on the following respawn.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1425297

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot
  (vivid/mako 110)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

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

[Dx-packages] [Bug 1348538] Re: [power] Display should come on when started charging

[Ricardo Salveti]

** No longer affects: indicator-power (Ubuntu)

** No longer affects: unity-system-compositor

** No longer affects: unity-system-compositor (Ubuntu)

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

** Also affects: powerd (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

Title:
  [power] Display should come on when started charging

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in powerd package in Ubuntu:
  New
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  The display should be triggered to turn on for a $timeout when
  connected to a charger, so that users can see charging commenced.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 25 09:45:42 2014
  SourcePackage: unity-system-compositor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1391501] Re: Calendar reminders should mute if phone is muted

[Ricardo Salveti]

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

Having a separated role would be a bit of rework on the rest of the
stack (pulse, etc), so we should just use the role 'alert' for now (same
as ringtone, camera click, etc).

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1391501

Title:
  Calendar reminders should mute if phone is muted

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Calendar reminders seem to use the alarm role, which means muting your
  phone does not impact them.

  It should either use the same role as the ringer, or maybe a
  completely separate one.

  This is related to bug #1291458.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-datetime 13.10.0+15.04.20141103-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 11 13:06:24 2014
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

  UX Solution:
  I would use a separate role.

  Calendar reminders are lower in priority than Ringer and Alarms and
  users should be able to silence them.

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

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

[Dx-packages] [Bug 1410874] Re: Alarm sounds vs Calendar sounds

[Ricardo Salveti]

>From bug 1391501 it seems we really should be using the role alert, as
calendar events are not really alarms. That would also mean that the
alert volume (default when nothing is playing) will also affect the
calendar events, which is also good.

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1410874

Title:
  Alarm sounds vs Calendar sounds

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  As discussed with rsalveti and pmcgowan in #phablet on 14 Jan

  There are two issues in the datetime notification code that need to be
  changed.

  1. Right now we only set role=alarm if the sound is looping; ie if it's an 
alarm clock event rather than calendar event.
  Set calendar event role to alert

  2. Calendar events shouldn't play in silent mode. We can test for
  silent mode on the bus, http://bazaar.launchpad.net/~phablet-team
  /telephony-
  service/trunk/view/head:/libtelephonyservice/greetercontacts.cpp has
  an example: getUserValue("com.ubuntu.touch.AccountsService.Sound",
  "SilentMode");

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

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

[Dx-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)

[Ricardo Salveti]

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

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

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1389008

Title:
  Often fails to connect to Pulseaudio and unity-notifications (results
  in missing volume notifications and improper volume control)

Status in the base for Ubuntu mobile products:
  New
Status in indicator-sound package in Ubuntu:
  Invalid
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in indicator-sound package in Ubuntu RTM:
  Invalid
Status in ubuntu-touch-session package in Ubuntu RTM:
  Confirmed
Status in unity8 package in Ubuntu RTM:
  Invalid

Bug description:
  Often after boot indicator-sound fails to connect to Pulseaudio and to
  unity-notifications using libnotify. Therefore, volume notifications
  aren't shown and changes to the volume role go unnoticed, which then
  results in improper volume control.

  As already mentioned in the original bug description, running "restart
  indicator-sound" resolves the issue.

  Original description:

  Happens often after phone boot where changing volume by touch or by
  phone buttons. Volume correctly changes, but the
  org.freedesktop.Notifications popup isn't displayed.

  The problem seems fixes itself if you run "restart indicator-sound",
  so maybe there's an issue with i-sound and unity-notifications
  starting at the same time, with the former querying the latter's
  capabilities before it's ready for business?

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

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

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

[Ricardo Salveti]

** Also affects: media-hub (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: media-hub (Ubuntu RTM)
   Status: New => Confirmed

** Changed in: media-hub (Ubuntu RTM)
   Importance: Undecided => Critical

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

Title:
  Make music controls work in the sound indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu RTM:
  Confirmed

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

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

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

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

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

[Ricardo Salveti]

For this to work on media-hub we first need to implement playlist
support, which is not trivial. Item available as part of the phone
foundations backlog.

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

Title:
  Make music controls work in the sound indicator

Status in “indicator-sound” package in Ubuntu:
  Incomplete
Status in “media-hub” package in Ubuntu:
  Confirmed

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

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

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

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

[Dx-packages] [Bug 1394105] Re: Sometimes significant lag between snap dialog and ringtone start

[Ricardo Salveti]

Please enable debug on pulse audio, retest, and give me back your
syslog. But please also save the timestamp when the dialog shows up, to
see if it was indeed pulse that got blocked or something like that.

To enable debug on pulse:
$ sudo sed -i 's/--start/--start --log-level=debug/g' 
/usr/share/upstart/sessions/pulseaudio.conf

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1394105

Title:
  Sometimes significant lag between snap dialog and ringtone start

Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  New
Status in “pulseaudio” package in Ubuntu:
  Incomplete
Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin

  When testing a large number of phone calls it could be seen that on
  certain calls there would be a significant delay between the snap
  decision dialog being displayed and the ringtone beginning to play.

  In extreme circumstances this could cause calls to be missed as there
  would not be enough time to answer.

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

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

[Dx-packages] [Bug 1391954] Re: indicator-sound not running on first boot

[Ricardo Salveti]

Can't reproduce this with mako, running the same image.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1391954

Title:
  indicator-sound not running on first boot

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Boot the device after a fresh flash with --wipe or --bootstrap
  2. Complete the wizard steps
  3. Check the indicators for the presence of the sound indicator

  Expected result:

  Sound indicator is present and running

  Actual result:

  Indicator is not present. There is a placeholder for it on the menu as
  shown in http://people.canonical.com/~brendan-donegan/indicator-
  sound.png

  Running 'status indicator-sound' shows it is stopped

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Nov 12 16:26:28 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-135345)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1391954] Re: indicator-sound not running on first boot

[Ricardo Salveti]

Actually no, just reproduced it, ignore my previous comment.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1391954

Title:
  indicator-sound not running on first boot

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Boot the device after a fresh flash with --wipe or --bootstrap
  2. Complete the wizard steps
  3. Check the indicators for the presence of the sound indicator

  Expected result:

  Sound indicator is present and running

  Actual result:

  Indicator is not present. There is a placeholder for it on the menu as
  shown in http://people.canonical.com/~brendan-donegan/indicator-
  sound.png

  Running 'status indicator-sound' shows it is stopped

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Nov 12 16:26:28 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-135345)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)

[Ricardo Salveti]

** Also affects: ubuntu-touch-session (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1389008

Title:
  Often fails to connect to Pulseaudio and unity-notifications (results
  in missing volume notifications and improper volume control)

Status in “indicator-sound” package in Ubuntu:
  Invalid
Status in “ubuntu-touch-session” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “indicator-sound” package in Ubuntu RTM:
  Invalid
Status in “ubuntu-touch-session” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Often after boot indicator-sound fails to connect to Pulseaudio and to
  unity-notifications using libnotify. Therefore, volume notifications
  aren't shown and changes to the volume role go unnoticed, which then
  results in improper volume control.

  As already mentioned in the original bug description, running "restart
  indicator-sound" resolves the issue.

  Original description:

  Happens often after phone boot where changing volume by touch or by
  phone buttons. Volume correctly changes, but the
  org.freedesktop.Notifications popup isn't displayed.

  The problem seems fixes itself if you run "restart indicator-sound",
  so maybe there's an issue with i-sound and unity-notifications
  starting at the same time, with the former querying the latter's
  capabilities before it's ready for business?

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

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

[Dx-packages] [Bug 1388235] Re: Battery icon turns red at 30%

[Ricardo Salveti]

I'd just follow what we have with some other phones, and showing low
battery only when < 15%

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

Title:
  Battery icon turns red at 30%

Status in Ubuntu UX bugs:
  Confirmed
Status in “indicator-power” package in Ubuntu:
  Confirmed

Bug description:
  This seems a bit pessimistic since the phone still has a great deal of
  capacity and time left, perhaps 15 or 20% is a better threshold

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

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

[Dx-packages] [Bug 1379618] Re: Sync to accountservice interferes with role volume changes (and device as well)

[Ricardo Salveti]

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

** Changed in: indicator-sound (Ubuntu RTM)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

** Changed in: indicator-sound (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: indicator-sound (Ubuntu RTM)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1379618

Title:
  Sync to accountservice interferes with role volume changes (and device
  as well)

Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu RTM:
  Confirmed

Bug description:
  When changing volume and either playing with role volume changes, or
  device connect/disconnect, the sync to accountservice can interfere
  with the volume level by restoring back the previous volume value set.

  One example:
  Setting volume (create_volume_action) - 0.180322
  Setting volume: 0.180322
  Setting volume internal (0.180322)
  Setting volume for role /org/pulseaudio/stream_restore1/entry2 (0.180322 - 
11817)
  Sending volume changed signal (0.180322 - 11817)
  Sending volume changed signal - active role 
(/org/pulseaudio/stream_restore1/entry3) changed (0.781906 - 51243)
  Setting volume internal (0.180322)
  Setting volume for role /org/pulseaudio/stream_restore1/entry3 (0.180322 - 
11817)
  Sending volume changed signal (0.180322 - 11817)

  To reproduce on touch:
  1) Without any active media stream, set volume (alert) to 10%
  2) Open music-app and play a song
  3) Change volume for the active stream (multimedia) to 90% and hit pause (you 
can do both from the indicator)
  4) The volume will change to 10% (as you paused multimedia), and then move 
back to 90%, as a consequence of the accountservice sync from the first volume 
set

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

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

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

[Ricardo Salveti]

Remember that silent mode here is used only by the 'alert' audio role.
The volume slider should still show up when the active role is
'multimedia', 'alarm' or 'phone'.

Ideally the silent mode would just mean a mute for the 'alert' role, but
this need further changes in ubuntu-system-settings and a few other
places.

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

Title:
  Volume slider still available when Silent Mode is on

Status in “indicator-sound” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged

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

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

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

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

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

[Dx-packages] [Bug 1373404] Re: No warning of high volume level

[Ricardo Salveti]

One easy way in the indicator to know if the active port a
headphone/headset: http://paste.ubuntu.com/8556022/

I think we should do the following:
1 - Check if the active port is headset;
2 - If headset, see if the volume for the multimedia role is higher than 75%. 
If higher, change it to 75% (this is basically what is done on Android). This 
check can be done once at every reboot (or every time someone plugs a 
headphone/headset).
3 - When changing volume for the multimedia role, warn the user if higher than 
75%.

You can also do the same for the other roles, but generally we are only
concerned with multimedia.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1373404

Title:
  No warning of high volume level

Status in Sound Menu:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid
Status in “unity-notifications” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

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

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

[Dx-packages] [Bug 1379618] [NEW] Sync to accountservice interferes with role volume changes (and device as well)

[Ricardo Salveti]

Public bug reported:

When changing volume and either playing with role volume changes, or
device connect/disconnect, the sync to accountservice can interfere with
the volume level by restoring back the previous volume value set.

One example:
Setting volume (create_volume_action) - 0.180322
Setting volume: 0.180322
Setting volume internal (0.180322)
Setting volume for role /org/pulseaudio/stream_restore1/entry2 (0.180322 - 
11817)
Sending volume changed signal (0.180322 - 11817)
Sending volume changed signal - active role 
(/org/pulseaudio/stream_restore1/entry3) changed (0.781906 - 51243)
Setting volume internal (0.180322)
Setting volume for role /org/pulseaudio/stream_restore1/entry3 (0.180322 - 
11817)
Sending volume changed signal (0.180322 - 11817)

To reproduce on touch:
1) Without any active media stream, set volume (alert) to 10%
2) Open music-app and play a song
3) Change volume for the active stream (multimedia) to 90% and hit pause (you 
can do both from the indicator)
4) The volume will change to 10% (as you paused multimedia), and then move back 
to 90%, as a consequence of the accountservice sync from the first volume set

** Affects: indicator-sound (Ubuntu)
 Importance: Critical
 Assignee: Ricardo Salveti (rsalveti)
 Status: Confirmed


** Tags: rtm14

** Changed in: indicator-sound (Ubuntu)
   Status: New => Confirmed

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

** Changed in: indicator-sound (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

** Tags added: rtm14

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1379618

Title:
  Sync to accountservice interferes with role volume changes (and device
  as well)

Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  When changing volume and either playing with role volume changes, or
  device connect/disconnect, the sync to accountservice can interfere
  with the volume level by restoring back the previous volume value set.

  One example:
  Setting volume (create_volume_action) - 0.180322
  Setting volume: 0.180322
  Setting volume internal (0.180322)
  Setting volume for role /org/pulseaudio/stream_restore1/entry2 (0.180322 - 
11817)
  Sending volume changed signal (0.180322 - 11817)
  Sending volume changed signal - active role 
(/org/pulseaudio/stream_restore1/entry3) changed (0.781906 - 51243)
  Setting volume internal (0.180322)
  Setting volume for role /org/pulseaudio/stream_restore1/entry3 (0.180322 - 
11817)
  Sending volume changed signal (0.180322 - 11817)

  To reproduce on touch:
  1) Without any active media stream, set volume (alert) to 10%
  2) Open music-app and play a song
  3) Change volume for the active stream (multimedia) to 90% and hit pause (you 
can do both from the indicator)
  4) The volume will change to 10% (as you paused multimedia), and then move 
back to 90%, as a consequence of the accountservice sync from the first volume 
set

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

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

[Dx-packages] [Bug 1337917] Re: Alarm does not ring when phone is muted

[Ricardo Salveti]

The volume part of it is described by bug 1368827.

** No longer affects: indicator-sound

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1337917

Title:
  Alarm does not ring when phone is muted

Status in Clock application for Ubuntu devices:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  I expect the alarm to go off even if the phone is muted.

  I am not sure if this is a simple fix or all the things mentioned at
  https://wiki.ubuntu.com/SilentMode need to be implemented first.

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

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

[Dx-packages] [Bug 1368827] Re: [FFe] [touch] indicator needs to be able to control volume per audio role

[Ricardo Salveti]

** Changed in: indicator-sound (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1368827

Title:
  [FFe] [touch] indicator needs to be able to control volume per audio
  role

Status in “indicator-sound” package in Ubuntu:
  In Progress

Bug description:
  Dear Release Team,

  I would like to request a FFe for indicator-sound, in order to deliver
  the remaining features needed for Ubuntu Touch.

  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

  This change is touch specific as it needs a combination of configs
  that are available in ubuntu-touch-session for it to be used
  (different code path that only gets used on touch).

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

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

[Dx-packages] [Bug 1368827] Re: [FFe] [touch] indicator needs to be able to control volume per audio role

[Ricardo Salveti]

** Summary changed:

- [touch] indicator needs to be able to control volume per audio role
+ [FFe] [touch] indicator needs to be able to control volume per audio role

** Changed in: indicator-sound (Ubuntu)
   Status: In Progress => New

** Description changed:

+ Dear Release Team,
+ 
  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to be
  able to change volume per audio roles, and not only the master volume.
  
  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume level
  for multimedia, ringtone and alarms.
  
  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/
  
  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py
  
  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.
+ 
+ This change is touch specific as it needs a combination of configs that
+ are available in ubuntu-touch-session for it to be used (different code
+ path that only gets used on touch).

** Description changed:

  Dear Release Team,
+ 
+ I would like to request a FFe for indicator-sound, in order to deliver
+ the remaining features needed for Ubuntu Touch.
  
  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to be
  able to change volume per audio roles, and not only the master volume.
  
  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume level
  for multimedia, ringtone and alarms.
  
  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/
  
  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py
  
  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.
  
  This change is touch specific as it needs a combination of configs that
  are available in ubuntu-touch-session for it to be used (different code
  path that only gets used on touch).

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1368827

Title:
  [FFe] [touch] indicator needs to be able to control volume per audio
  role

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Dear Release Team,

  I would like to request a FFe for indicator-sound, in order to deliver
  the remaining features needed for Ubuntu Touch.

  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

  This change is touch specific as it needs a combination of configs
  that are available in ubuntu-touch-session for it to be used
  (different code path that only gets used on touch).

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

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

[Dx-packages] [Bug 1368827] Re: [touch] indicator needs to be able to control volume per audio role

[Ricardo Salveti]

MRs:
* 
https://code.launchpad.net/~rsalveti/indicator-sound/adding-support-for-sound-per-roles/+merge/235562
* 
https://code.launchpad.net/~rsalveti/ubuntu-touch-session/changing-config-allow-volume-per-role/+merge/235563
* 
https://code.launchpad.net/~rsalveti/telepathy-ofono/remove-initial-voice-volume/+merge/235564

And all available at silo 18 (https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-018).

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1368827

Title:
  [touch] indicator needs to be able to control volume per audio role

Status in “indicator-sound” package in Ubuntu:
  In Progress

Bug description:
  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

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

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

[Dx-packages] [Bug 1368827] Re: [touch] indicator needs to be able to control volume per audio role

[Ricardo Salveti]

** Changed in: indicator-sound (Ubuntu)
   Importance: High => Critical

** Changed in: indicator-sound (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1368827

Title:
  [touch] indicator needs to be able to control volume per audio role

Status in “indicator-sound” package in Ubuntu:
  In Progress

Bug description:
  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

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

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

[Dx-packages] [Bug 1368827] Re: [touch] indicator needs to be able to control volume per audio role

[Ricardo Salveti]

** Changed in: indicator-sound (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1368827

Title:
  [touch] indicator needs to be able to control volume per audio role

Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

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

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

[Dx-packages] [Bug 1368827] [NEW] [touch] indicator needs to be able to control volume per audio role

[Ricardo Salveti]

Public bug reported:

>From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
we need to change the default behaviour of the indicator in order to be
able to change volume per audio roles, and not only the master volume.

On touch the master volume will always be at 100%, and each media role
will have its own volume values, so we can have a different volume level
for multimedia, ringtone and alarms.

This can be done using the streamrestore module in pulseaudio (via another dbus 
entry point that is only enabled on touch atm):
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

There's also a sample script on python that can be used to set/get volume per 
roles:
https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

And the current roles supporter by touch are: multimedia, alert, phone
and alarm.

** Affects: indicator-sound (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: rtm14 touch-2014-09-25

** Tags added: rtm14 touch-2014-09-25

** Changed in: indicator-sound (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-sound (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1368827

Title:
  [touch] indicator needs to be able to control volume per audio role

Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

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

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

[Dx-packages] [Bug 1337917] Re: Alarm does not ring when phone is muted

[Ricardo Salveti]

** Tags added: rtm14 touch-2014-09-18

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1337917

Title:
  Alarm does not ring when phone is muted

Status in Sound Menu:
  Triaged
Status in Clock application for Ubuntu devices:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  I expect the alarm to go off even if the phone is muted.

  I am not sure if this is a simple fix or all the things mentioned at
  https://wiki.ubuntu.com/SilentMode need to be implemented first.

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

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

[Dx-packages] [Bug 1358293] Re: Turning off Bluetooth in the Indicator Crashes the Phone

[Ricardo Salveti]

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-bluetooth (Ubuntu)
 Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)

** Changed in: indicator-bluetooth (Ubuntu)
   Importance: Undecided => High

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

Title:
  Turning off Bluetooth in the Indicator Crashes the Phone

Status in “indicator-bluetooth” package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Enable a bluetooth headset or earbuds
  2. Start the music player and play an album
  3. Confirm that the music is playing
  4. Turn off the screen and listen to the music for a few tracks
  5. Turn on the screen and pause the music player
  6. Pull down the indicator and try to disable bluetooth

  The indicator freezes for a time, then the whole phone reboots

  root@ubuntu-phablet:/# cat /proc/last_kmsg   
  ram console header, hw_status: 2, fiq step 40.
  bin log 0.
  x104) from [] (dump_stack+0x20/0x24)
  [ 1164.156265] (1)[2070:unity8][] (dump_stack+0x20/0x24) from 
[] (handle_IPI+0x21c/0x250)
  [ 1164.157473] (1)[2070:unity8][] (handle_IPI+0x21c/0x250) from 
[] (do_IPI+0x18/0x1c)
  [ 1164.158638] (1)[2070:unity8][] (do_IPI+0x18/0x1c) from 
[] (__irq_usr+0x34/0xc0)
  [ 1164.160851] (0)[2053:indicator-bluet]init emmc for ipanic dump
  [ 1164.175534] (0)[2053:indicator-bluet][pll]0xF020924C = 0x8001
  [ 1164.176285] (0)[2053:indicator-bluet][pll]0xF0209240 = 0x121
  [ 1164.176992] (0)[2053:indicator-bluet][mux] 0xF060 = 0x1818100
  [ 1164.177749] (0)[2053:indicator-bluet][mux] 0xF070 = 0x81808101
  [ 1164.178519] (0)[2053:indicator-bluet][clk] 0xF0003010 = 0x0
  [ 1164.179213] (0)[2053:indicator-bluet][clk] 0xF0003018 = 0x2fecffd
  [ 1164.180068] (0)[2053:indicator-bluet]send cmd0
  [ 1164.184692] (0)[2053:indicator-bluet]cmd1: resp(0xff8080), i=500
  [ 1164.185430] (0)[2053:indicator-bluet]send cmd0
  [ 1164.213984] (0)[2053:indicator-bluet]cmd1: resp(0xc0ff8080), i=498
  [ 1164.216746] (0)[2053:indicator-bluet]resp: 0x11010030 0x30384739 
0x32009acc 0xa9373149
  [ 1164.240817] (0)[2053:indicator-bluet]read fifo done, wait xfer_compl 
interrupt
  [ 1164.241712] (0)[2053:indicator-bluet]emmc offset (0x5c00)
  [ 1164.244389] (0)[2053:indicator-bluet]init eMMC success
  [ 1167.466826] (0)[2053:indicator-bluet]card_dump_func_write failed (18), 
size: 0x58000
  [ 1167.467803] (0)[2053:indicator-bluet]CPU: 0Tainted: GW 
(3.4.67 #1)
  [ 1167.468745] (0)[2053:indicator-bluet]PC is at l2cap_chan_destroy+0x3c/0x88
  [ 1167.469599] (0)[2053:indicator-bluet]LR is at __raw_write_lock+0x34/0xa8
  [ 1167.470437] (0)[2053:indicator-bluet]pc : []lr : 
[]psr: 600f0013
  [ 1167.470444] (0)[2053:indicator-bluet]sp : d8897d68  ip : 00100100  fp : 
d8897d7c
  [ 1167.472412] (0)[2053:indicator-bluet]r10: cc583a20  r9 : cf9db800  r8 : 
c74e1300
  [ 1167.473335] (0)[2053:indicator-bluet]r7 : 0067  r6 : c74e13bc  r5 : 
cc58380c  r4 : cc583800
  [ 1167.474419] (0)[2053:indicator-bluet]r3 : 00200200  r2 : 00100100  r1 : 
00200200  r0 : c1128f40
  [ 1167.475505] (0)[2053:indicator-bluet]Flags: nZCv  IRQs on  FIQs on  Mode 
SVC_32  ISA ARM  Segment user
  [ 1167.476664] (0)[2053:indicator-bluet]Control: 10c5387d  Table: 8ddd806a  
DAC: 0015
  [ 1167.480769] (0)[2053:indicator-bluet]Process indicator-bluet (pid: 2053, 
stack limit = 0xd8896300)
  [ 1167.481881] (0)[2053:indicator-bluet]Stack: (0xd8897d68 to 0xd8898000)
  [ 1167.482697] (0)[2053:indicator-bluet]7d60:   0009 
cf548400 d8897d94 d8897d80 c07ac5b8 c07a6aac
  [ 1167.483989] (0)[2053:indicator-bluet]7d80: 0002 cc583800 d8897da4 
d8897d98 c07ac690 c07ac580 d8897ddc d8897da8
  [ 1167.485279] (0)[2053:indicator-bluet]7da0: c07a2fc8 c07ac684 c74e13c4 
d00bf400 d8897ddc d00bf400 d6dd6d00 d6dd6d00
  [ 1167.486570] (0)[2053:indicator-bluet]7dc0: 0009 d6dd6808 d8897f78 
d6dd6828 d8897df4 d8897de0 c07aa9dc c07a2f0c
  [ 1167.487861] (0)[2053:indicator-bluet]7de0: d6dd6cec d00bf400 d8897e14 
d8897df8 c0793444 c07aa9bc d6dd6800 d6dd6ecc
  [ 1167.489151] (0)[2053:indicator-bluet]7e00: 0008 d6dd6ca0 d8897e4c 
d8897e18 c078ee50 c07933a8 d8897e34 c07f9818
  [ 1167.490442] (0)[2053:indicator-bluet]7e20: d8897e4c dbdb7600 0001 
0008 d883e0c0 0008 d8897f78 be9d7e48
  [ 1167.491733] (0)[2053:indicator-bluet]7e40: d8897e5c d8897e50 c078f094 
c078ed90 d8897e74 d8897e60 c07e270c c078f080
  [ 1167.493023] (0)[2053:indicator-bluet]7e60: dbdb7600 c0c59bb0 d8897e9c 
d8897e78 c07e288c c07e2688  00010302
  [ 1167.494314] (0)[2053:indicator-bluet]7e80: d883e0c0 0008 c07e2774 
d8896000 d8897f6c d8897ea0 c0147b30 c07e2780
  [ 1167.495605] (0)[2053:indicator-bluet]7ea0: d8896000 d9f1ed04 d8897ec4 
d8897eb8 c07f98b0 c07f932c d8897ed4 d8897ec8
  [ 1167.496895] (0)[2053:indicator-bluet]7ec0: c09abcb8 c09

[Dx-packages] [Bug 1333303] Re: [touch] indicator not storing/restoring volume per sink-port

[Ricardo Salveti]

On touch, as it is single-user mode for now, we could just let pulse do
all the store/restore handling, but that would possibly break the
desktop and the convergence model.

There is also another issue that the greeter would need to be able to
control the main volume independently, and that conflicts with the way
pulse is currently handling the volume settings (as we have a pulse per
user).

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/103

Title:
  [touch] indicator not storing/restoring volume per sink-port

Status in Sound Menu:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  By design the indicator-sound is only storing/restoring the master
  volume, not handing sink-port specifics.

  Meanwhile we have pulse also storing/restoring the per sink-port
  values once the daemon is started, but it gets reset again once
  indicator-sound is started with the system-wide value stored by the
  indicator.

  This is a problem with ubuntu touch specifically, because of the following 
use case scenario:
  - Set speaker volume to 90 % using the indicator
  - Connect wired headset, set volume to 10%
  - Disconnect wired headset, volume will change to 90% automatically (because 
of pulse)
  - Reboot with the wired headset connected

  After boot the volume will be 90% instead of 10%.

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

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

[Dx-packages] [Bug 1333303] [NEW] [touch] indicator not storing/restoring volume per sink-port

[Ricardo Salveti]

Public bug reported:

By design the indicator-sound is only storing/restoring the master
volume, not handing sink-port specifics.

Meanwhile we have pulse also storing/restoring the per sink-port values
once the daemon is started, but it gets reset again once indicator-sound
is started with the system-wide value stored by the indicator.

This is a problem with ubuntu touch specifically, because of the following use 
case scenario:
- Set speaker volume to 90 % using the indicator
- Connect wired headset, set volume to 10%
- Disconnect wired headset, volume will change to 90% automatically (because of 
pulse)
- Reboot with the wired headset connected

After boot the volume will be 90% instead of 10%.

** Affects: indicator-sound
 Importance: High
 Assignee: Ted Gould (ted)
 Status: Confirmed

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/103

Title:
  [touch] indicator not storing/restoring volume per sink-port

Status in Sound Menu:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  By design the indicator-sound is only storing/restoring the master
  volume, not handing sink-port specifics.

  Meanwhile we have pulse also storing/restoring the per sink-port
  values once the daemon is started, but it gets reset again once
  indicator-sound is started with the system-wide value stored by the
  indicator.

  This is a problem with ubuntu touch specifically, because of the following 
use case scenario:
  - Set speaker volume to 90 % using the indicator
  - Connect wired headset, set volume to 10%
  - Disconnect wired headset, volume will change to 90% automatically (because 
of pulse)
  - Reboot with the wired headset connected

  After boot the volume will be 90% instead of 10%.

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

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

[Dx-packages] [Bug 1295122] Re: Alarms not going off reliably on recent touch images

[Ricardo Salveti]

Can you guys try to reproduce this issue after running 'powerd-cli
active' (as root) on another terminal?

Just to understand if this is related with the device going into deep
suspend or not, as it's expected to be broken in case the device is
fully suspended (no support for hw alarms yet).

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1295122

Title:
  Alarms not going off reliably on recent touch images

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Alarms are not reliable on recent images on touch.

  Popey: See's the alarm notification but not hears no sound.
  davmor2: I see and hear the alarm and notification if the device is awake if 
the screen is blank though I sometimes get an alarm 2 minutes Plus after the 
alarm was meant to go off other times I neither see nor hear the alarm.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Thu Mar 20 13:12:36 2014
  InstallationDate: Installed on 2014-03-20 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1253810] Re: Messages in Incoming not always display the correct date and content

[Ricardo Salveti]

The timestamp is correct from ofono, and the message is also displayed
correctly in the messaging app, seems the bug is indeed in the
indicator.

And I could easily reproduce the problem today.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1253810

Title:
  Messages in Incoming not always display the correct date and content

Status in The Messaging Menu:
  New
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes SMSes are displayed with Dec 31 as a date and the content is
  not displayed. This happens every once in a while, in general the
  notifications are displayed correctly, but as I exchanged a lot of
  SMSes with different numbers, this problem happened a few times.

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

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

[Dx-packages] [Bug 1253810] Re: Messages in Incoming not always display the correct date and content

[Ricardo Salveti]

Probably a regression, as it's the first time I had this issue.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1253810

Title:
  Messages in Incoming not always display the correct date and content

Status in The Messaging Menu:
  New
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes SMSes are displayed with Dec 31 as a date and the content is
  not displayed. This happens every once in a while, in general the
  notifications are displayed correctly, but as I exchanged a lot of
  SMSes with different numbers, this problem happened a few times.

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

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

[Dx-packages] [Bug 1253810] Re: Messages in Incoming not always display the correct date and content

[Ricardo Salveti]

Confirming bug with r32.

** Attachment added: "indicator.png"
   
https://bugs.launchpad.net/indicator-messages/+bug/1253810/+attachment/3917762/+files/indicator.png

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

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1253810

Title:
  Messages in Incoming not always display the correct date and content

Status in The Messaging Menu:
  New
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes SMSes are displayed with Dec 31 as a date and the content is
  not displayed. This happens every once in a while, in general the
  notifications are displayed correctly, but as I exchanged a lot of
  SMSes with different numbers, this problem happened a few times.

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

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

[Dx-packages] [Bug 1253804] Re: Indicator icons don't match the settings they display

[Ricardo Salveti]

Critical as it's a regression.

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

** Summary changed:

- Indicator icons don't match the settings they display
+ [regression] Indicator icons don't match the settings they display

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1253804

Title:
  [regression] Indicator icons don't match the settings they display

Status in Ubuntu UX bugs:
  New
Status in The Unity 8 shell:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  In the top bar I have these icons: network (mobile, wifi), bluetooth,
  location, incoming, battery, sound and clock. When I drop down to
  access the settings, the only one that shows the correct panel is
  Network. All the others display settings different than what the icon
  implies. For example, Bluetooth icon displays Incoming settings,
  Location displays Bluetooth, Incoming displays Battery, Battery
  displays Upcoming, Sound displays Location and the Clock displays
  Sound settings.

  I'm using mako, -proposed, r27, read-only.

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

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

[Dx-packages] [Bug 1223560] Re: Battery indicator shows low battery when plugged in during boot

[Ricardo Salveti]

Confirming the issues, this is quite annoying.

** Changed in: touch-preview-images
   Status: New => Confirmed

** Changed in: touch-preview-images
   Importance: Undecided => High

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

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

Title:
  Battery indicator shows low battery when plugged in during boot

Status in Touch Preview Images:
  Confirmed
Status in “indicator-power” package in Ubuntu:
  New

Bug description:
  I bootstrapped a maguro with the 20130905.1 images, and when it came
  up, the battery indicator showed a small red bar with a charging icon,
  even though the battery was full.  If I unplug it and plug it back in,
  it shows a full/charging icon.  If I boot up with it not plugged in,
  it shows the expected icons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/touch-preview-images/+bug/1223560/+subscriptions

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

[Dx-packages] [Bug 1221871] Re: indicator-power-service is a lightly busy all the time

[Ricardo Salveti]

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

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

Title:
  indicator-power-service is a lightly busy all the time

Status in Touch Preview Images:
  New
Status in “indicator-power” package in Ubuntu:
  New

Bug description:
  In a vain attempt to reduce power on these phone devices I noticed
  that indicator-power-service is using just under 1% of one CPU all the
  time.

   CPU usage:
    PID  ProcessUSR%   SYS%  TOTAL%
    1358 indicator-power-serv   0.05   0.04   0.08 (very light load)

  It seems to be waiting on poll() on a couple of threads which
  cumulatively add up to about 1.68 wakeups a second over a 1 hour
  analysis:

  Top polling system calls:

  PID 
    1369 indicator-power-serv poll1.3462 polls/sec
    1358 indicator-power-serv poll0.3376 polls/sec
   Total  1.6838 polls/sec

  This contributes to a bunch of context switching by these threads:

  Context Switches:
    PID  ProcessVoluntary   Involuntary Total
   Ctxt Sw/Sec  Ctxt Sw/Sec  Ctxt Sw/Sec
    1369 indicator-power-serv10.75 0.1510.90 (moderate)
    1358 indicator-power-serv 3.53 0.07 3.60 (low)
    1372 indicator-power-serv 0.00 0.00 0.00 (idle)
   Total 14.29 0.2214.50

  [ See the attached log, launchpad formatting sucks ]

  I also observed a couple of brk() calls, and a small amount of heap
  growth which may indicate it has a small memory leak, but I am
  speculating on this.

  Attached is a full report from a 1 hour of monitoring indicator-power-
  service for reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/touch-preview-images/+bug/1221871/+subscriptions

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