[Dx-packages] [Bug 1477433] Re: Alarm does not ring when the phone is off

[Michael Zanetti]

FWIW, at least for krillin once I did the research and it seems that the
chip does support setting an alarm time (similar to a PC's RTC clock)
where the device powers itself on.

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

Title:
  Alarm does not ring when the phone is off

Status in Canonical System Image:
  New
Status in Ubuntu Clock App:
  Invalid
Status in indicator-datetime package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The alarm does not work when the phone is off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1477433/+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 1477433] Re: Alarm does not ring when the phone is off

[Michael Zanetti]

Reopening as this is still an issue.

Yes, off as in really off. Every Nokia or Blackberry device was able to
turn itself on and ring the alarm. IMO this is really important,
otherwise the alarm on the phone is not trustworthy at all.

** Changed in: indicator-datetime (Ubuntu)
   Status: Expired => New

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

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

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

Title:
  Alarm does not ring when the phone is off

Status in Canonical System Image:
  New
Status in Ubuntu Clock App:
  Invalid
Status in indicator-datetime package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The alarm does not work when the phone is off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1477433/+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 1465858] Re: Time can not be read when alarm is set (while swiping/opening indicator)

[Michael Zanetti]

Wouldnt it make sense to just keep it looking the same as when there is
no alarm set? IMO its just about hiding the clock icon instaed of the
time and always behaving the same, regardless if there is an alarm set
or not. I totally agree with this bug that it should show the clock and
not the alarm icon in the expandet state. Especially since in the
expanded state the user can still see any upcoming alarms but atm the
time information is completely hidden.

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

Title:
  Time can not be read when alarm is set (while swiping/opening
  indicator)

Status in Unity 8:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I am on krillin r23 stable (OTA-4), but I have reproduced this bug on
  mako (stable channel) too.

  0. launch a full screen app like Machine Vs Machines. NO alarm set.
  1. can't see the time (expected) because when in full screen: top bar 
indicator is hidden
  2. swipe from top edge and focus time indicator: you can read the time at the 
top of the time label indicator (expected)

  Now

  0. launch a full screen app like Machine Vs Machines. At least 1 alarm is set 
and due in the futur.
  1. can't see the time (expected) because when in full screen : top bar 
indicator is hidden
  2. swipe from top edge and focus time indicator: you can't read the time at 
the top of the time label's indicator because the time is replaced by the alarm 
icon (not expected)

  Current UX to see the time (alternative solution until it get fixed):

  3. swipe from left side, and focus another app not in full screen (or go 
scope with left swipe)
  4. see time from top bar indicators.
  5. swipe from right to get back at your focused apps.

  Or :
  3. push power (screen off)
  4. push power (screen on, lock screen)
  5. check the time at the top bar indicator
  6. unlock to get back to yout focused app.

  5 or 6  steps are needed to just watch the time while only 1or2 could
  do the work if the time was always shown on the indicator time's icon.

  I beleive this is not a niche need :
   * Alarms are usual
   * Full screen apps too
   * checking time too

  PS: please affect the bug to indicator if needed, It fails when I
  tryed submit from here https://bugs.launchpad.net/ubuntu/+source
  /indicator-time/+filebug

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8/+bug/1465858/+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 1465858] Re: Time can not be read when alarm is set (while swiping/opening indicator)

[Michael Zanetti]

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

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

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

Title:
  Time can not be read when alarm is set (while swiping/opening
  indicator)

Status in Unity 8:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I am on krillin r23 stable (OTA-4), but I have reproduced this bug on
  mako (stable channel) too.

  0. launch a full screen app like Machine Vs Machines. NO alarm set.
  1. can't see the time (expected) because when in full screen: top bar 
indicator is hidden
  2. swipe from top edge and focus time indicator: you can read the time at the 
top of the time label indicator (expected)

  Now

  0. launch a full screen app like Machine Vs Machines. At least 1 alarm is set 
and due in the futur.
  1. can't see the time (expected) because when in full screen : top bar 
indicator is hidden
  2. swipe from top edge and focus time indicator: you can't read the time at 
the top of the time label's indicator because the time is replaced by the alarm 
icon (not expected)

  Current UX to see the time (alternative solution until it get fixed):

  3. swipe from left side, and focus another app not in full screen (or go 
scope with left swipe)
  4. see time from top bar indicators.
  5. swipe from right to get back at your focused apps.

  Or :
  3. push power (screen off)
  4. push power (screen on, lock screen)
  5. check the time at the top bar indicator
  6. unlock to get back to yout focused app.

  5 or 6  steps are needed to just watch the time while only 1or2 could
  do the work if the time was always shown on the indicator time's icon.

  I beleive this is not a niche need :
   * Alarms are usual
   * Full screen apps too
   * checking time too

  PS: please affect the bug to indicator if needed, It fails when I
  tryed submit from here https://bugs.launchpad.net/ubuntu/+source
  /indicator-time/+filebug

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8/+bug/1465858/+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 1480137] Re: Reminder alarm rings about 20 seconds behind of the real system time

[Michael Zanetti]

The actual ringing is done by the alarms service (indicator-datetime).
Marking as invalid for the notes app.

** Also affects: indicator-datetime
   Importance: Undecided
   Status: New

** Project changed: indicator-datetime => indicator-datetime (Ubuntu)

** Changed in: reminders-app
   Status: New => Invalid

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

Title:
  Reminder alarm rings about 20 seconds behind of the real system time

Status in Ubuntu Notes app:
  Invalid
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  $ system-image-cli -i
  current build number: 163
  device name: krillin
  channel: ubuntu-touch/devel-proposed/krillin.en
  last update: 2015-07-31 04:05:27
  version version: 163
  version ubuntu: 20150731
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

  Steps to reproduce:
  1. Launch Notes app from Apps scope
  2. Swipe up from bottom to add a note
  3. Select date and time for the reminder
  4. Save and get the note done
  5. Wait for the reminder alarm to trigger
  6. When it's ringing check if the time is consistent with real system time

  Expected results:
  The time of reminder alarm ringing is consistent with real system time

  Actual results:
  The time of reminder alarm ringing is about 20 seconds behind the real system 
time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/reminders-app/+bug/1480137/+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 1317860] Re: the phone should switch itself off before completely draining battery

[Michael Zanetti]

It is not limited to frieza. Once you have 3 or 4 developer devices, you
will frequently run into this issue. Whenever you need to test something
on that particular device, rest assured it wants to be charged for 10
mins before turning on :)

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

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

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list

[Michael Zanetti]

** Also affects: ubuntu-ux
   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/1541125

Title:
  Clicking a date in the new calendar doesn't change the indicator's
  appointment list

Status in Ubuntu UX:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Now that we've got a calendar in indicator-datetime in Unity 8, there
  are a few features from Unity 7 that we should decide if/how we're
  goint to handle in Unity 8.

  * Show Week Numbers
  * Highlight days of the month that include appointments
  * Unity tells indicator-datetime what calendar day has been clicked so that 
the "upcoming appointments" list can be adjusted accordingly

  These are currently implemented as fields in a GAction state
  dictionary and documented in http://bazaar.launchpad.net/~indicator-
  applet-developers/indicator-datetime/trunk.15.10/view/head:/README ...
  however that was all done for Unity 7, and IMO it would make sense to
  improve the unity<->indicator API here so that Unity8 doesn't have to
  deal with key-variant map GAction states.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1541125/+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 1540942] Re: Showing the remaining power percentage

[Michael Zanetti]

The indicator supports this already. It is hidden intentionally right now. It 
can be enabled by calling:
gsettings set com.canonical.indicator.power show-percentage true

Adding Ubuntu-UX to decide whether we want this configurable via UI.

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

** Changed in: indicator-power (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: ubuntu-ux
   Status: New => Confirmed

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

Title:
  Showing the remaining power percentage

Status in Ubuntu UX:
  Confirmed
Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  It's very useful add an option for showing the remaining power percentage, 
near the power indicator.
  Watch the pic attached below, this is what happen in android devices.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1540942/+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 1480200] Re: indicator-datetime starting ringing almost immediately if timer is set for less than 60 seconds

[Michael Zanetti]

To be clear, it's not "less than 60 seconds". As the duplicate of this
report correctly states, this happens if the alarm is scheduled within
the current minute.

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

** Also affects: canonical-developer-experience
   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/1480200

Title:
  indicator-datetime starting ringing almost immediately if  timer is
  set for less than 60 seconds

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  New
Status in Timer:
  Confirmed
Status in Ubuntu Clock App:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  indicator-datetime doesn't check seconds for alarms.

  Steps to reproduce:
  1. Install Timer: https://uappexplorer.com/app/timer.mivoligo
  2. Set timer to 15 seconds
  3. Start timer

  Currently:
  4. Alarm is ringing almost immediately (it is not always reproducible)

  Expected:
  4. Alarm is ringing after 15 seconds

  It is an blocker for Timer implementation in Clock app:
  https://bugs.launchpad.net/ubuntu-clock-app/+bug/1427566

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1480200/+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 1480200] Re: indicator-datetime starting ringing almost immediately if timer is set in current minute

[Michael Zanetti]

It's all we have atm. I could imagine it as a timer api but it would
probably require better precision (it's off up to 5 seconds in some
cases atm) and some other fixes (like calling back the originating app
on clicking the notification, instead of the clock app). Also it has the
side effect that such timers will show up as alarms in the datetime
indicator and iirc the clock app. Both of them are probably questions
for design. On the other hand, a proper timer api could offer better
features I think. Depends if we want to allow, e.g. focusing/resuming
the app when the timer is due so other things could be done instead of
just ringing a notification.

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

Title:
  indicator-datetime starting ringing almost immediately if  timer is
  set in current minute

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Incomplete
Status in Timer:
  Confirmed
Status in Ubuntu Clock App:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  indicator-datetime doesn't check seconds for alarms.

  Steps to reproduce:
  1. Install Timer: https://uappexplorer.com/app/timer.mivoligo
  2. Set timer to 15 seconds in current minute
  3. Start timer

  Currently:
  4. Alarm is ringing almost immediately (it is not always reproducible)

  Expected:
  4. Alarm is ringing after 15 seconds

  It is an blocker for Timer implementation in Clock app:
  https://bugs.launchpad.net/ubuntu-clock-app/+bug/1427566

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1480200/+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 1530807] Re: Bluetooth cannot be activated.

[Michael Zanetti]

some more information: Bluetooth only appears being off in the indicator
and the settings. It is, in fact on and working just fine.

This screenshot was taken while a Bluetooth keyboard was connected and
functional: http://i.imgur.com/EIUnG9n.png

Note the hciconfig output in the terminal. It shows that it is up and
running, and even doing the inquiry as instructed by the systemsettings
app. It's just that the app and indicator think its off.

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

Title:
  Bluetooth cannot be activated.

Status in Canonical System Image:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior: 
  Bluetooth slider is moved to on
  Activity spinners appear 
  Bluetooth slider moves to off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1530807/+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 1317860] Re: the phone should switch itself off before completely draining battery

[Michael Zanetti]

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

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

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

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1420169] Re: Alarms don't set RTC alarm to wake up the phone

[Michael Zanetti]

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

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

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

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

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

  This causes alarms to be lost.

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

-- 
Mailing list: https://launchpad.net/~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 1504057] [NEW] Bluetooth icon should turn blue when there's traffic happening

[Michael Zanetti]

Public bug reported:

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

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

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

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

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

Status in indicator-bluetooth package in Ubuntu:
  New

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1478506] Re: Apps change audio output role all the time

[Michael Zanetti]

This bug is about an issue in the implementation that whenever someone
creates a new "Audio" or "SoundEffect" item (regardless of the role) it
will change the volume. The game maroon in trouble, as mentioned in the
original bug description only uses SoundEffects, no Audio. Yet it
changes the volume all the time. Please do not change the topic for this
bug to some role-discussion. We have other bugs for that. I've moved the
discussion to the phone mailing list.

** Summary changed:

- Apps change audio output role all the time
+ Apps change volume all the time

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

Title:
  Apps change volume all the time

Status in Canonical System Image:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  To reproduce, install the app "Maroon in trouble" from the app store
  and play it a little with having sound enabled. Press the volume down
  hardware button on the phone. It will temporarily decrease the volume.
  However, whenever a new item comes into the scene, it will be on 100%
  volume again.

  Setting the system volume to 0 should keep everything at 0.

  
  Please note that this app does *not* have any code to set the volume! Also 
this app is one of the upstream Qt QML example demo apps, so this is really how 
QML apps are supposed to work (in other words, it is not a badly implemented 
app, but really an issue in the system)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506/+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 1478506] Re: Apps change audio output role all the time

[Michael Zanetti]

I don't think we want to change the SoundEffect to the alert role. That
would make things even more complicated and not really help with this
bug. Also that would have the side effect that in order to mute a game
one has to mute the ringtone, which IMO are really not the same thing.

Also muting a game with some background music and sound effects (e.g.
Machines vs. Machines) would require both, the alert and the multimedia
slider to be muted.

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

Title:
  Apps change audio output role all the time

Status in Canonical System Image:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  To reproduce, install the app Maroon in trouble from the app store
  and play it a little with having sound enabled. Press the volume down
  hardware button on the phone. It will temporarily decrease the volume.
  However, whenever a new item comes into the scene, it will be on 100%
  volume again.

  Setting the system volume to 0 should keep everything at 0.

  
  Please note that this app does *not* have any code to set the volume! Also 
this app is one of the upstream Qt QML example demo apps, so this is really how 
QML apps are supposed to work (in other words, it is not a badly implemented 
app, but really an issue in the system)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506/+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 1478075] Re: Sound indicator should only indicate ringtone volume

[Michael Zanetti]

I think there should be two sliders in the indicator. One for ringtone
volume, one for all multimedia sound.

** 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 indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1478075

Title:
  Sound indicator should only indicate ringtone volume

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in indicator-sound package in Ubuntu:
  New

Bug description:
  On the phone, the volume indicator follows the current active stream
  volume (music, alarm etc.) to show and control via slider and/or
  volume buttons.

  The indicator icon and slider should only ever follow the ringtone
  volume. I'm not sure whether volume buttons should work for alarms.

  This is somewhat related to bug #1291458.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150508-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[{'running': false, 'state': 'Paused'}]), 'mute': (true, '', [false]), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [1.0]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', [false]), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [{'running': false, 
'state': 'Paused'}]), 'play.mediaplayer-app.desktop': (true, '', 
['Paused']), 'volume': (true, 'i', [0.7414398193359375]), 
'next.mediaplayer-app.desktop': (true, '', []), 'indicator-shown': (true, '', 
[false]), 'root': (true, '', [{'title': 'Dźwięk', 'accessible-desc': 
'Głośność (74%)', 'icon': ('themed', ['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']), 'visible': true}]), 
'silent-mode': (true, '', [false]), 'previous.mediaplayer-app.desktop': 
(true, '', [])},)
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: armhf
  Date: Fri Jul 24 18:07:15 2015
  InstallationDate: Installed on 2015-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150723-020304)
  SourcePackage: indicator-sound
  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/1478075/+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 1465858] Re: Time can not be read when alarm is set (while swiping/opening indicator)

[Michael Zanetti]

** Package changed: unity8 (Ubuntu) = indicator-datetime (Ubuntu)

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

Title:
  Time can not be read when alarm is set (while swiping/opening
  indicator)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I am on krillin r23 stable (OTA-4), but I have reproduced this bug on
  mako (stable channel) too.

  0. launch a full screen app like Machine Vs Machines. NO alarm set.
  1. can't see the time (expected) because when in full screen: top bar 
indicator is hidden
  2. swipe from top edge and focus time indicator: you can read the time at the 
top of the time label indicator (expected)

  Now

  0. launch a full screen app like Machine Vs Machines. At least 1 alarm is set 
and due in the futur.
  1. can't see the time (expected) because when in full screen : top bar 
indicator is hidden
  2. swipe from top edge and focus time indicator: you can't read the time at 
the top of the time label's indicator because the time is replaced by the alarm 
icon (not expected)

  Current UX to see the time (alternative solution until it get fixed):

  3. swipe from left side, and focus another app not in full screen (or go 
scope with left swipe)
  4. see time from top bar indicators.
  5. swipe from right to get back at your focused apps.

  Or :
  3. push power (screen off)
  4. push power (screen on, lock screen)
  5. check the time at the top bar indicator
  6. unlock to get back to yout focused app.

  5 or 6  steps are needed to just watch the time while only 1or2 could
  do the work if the time was always shown on the indicator time's icon.

  I beleive this is not a niche need :
   * Alarms are usual
   * Full screen apps too
   * checking time too

  PS: please affect the bug to indicator if needed, It fails when I
  tryed submit from here https://bugs.launchpad.net/ubuntu/+source
  /indicator-time/+filebug

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

-- 
Mailing list: https://launchpad.net/~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 1461682] Re: [MX4] LED does not notify for incoming notifications

[Michael Zanetti]

According to ogra we can control the light using: /sys/class/leds/mx-
led/trigger

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

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

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

Bug description:
  Image r12

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

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

-- 
Mailing list: https://launchpad.net/~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 1461682] Re: [MX4] LED does not notify for incoming notifications

[Michael Zanetti]

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

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

LIGHT_ID_BACKLIGHT  
LIGHT_ID_KEYBOARD   
LIGHT_ID_BUTTONS
LIGHT_ID_BATTERY
LIGHT_ID_NOTIFICATIONS  
LIGHT_ID_ATTENTION  

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

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

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

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

Bug description:
  Image r12

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

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

-- 
Mailing list: https://launchpad.net/~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 1420169] Re: Alarms don't set RTC alarm to wake up the phone

[Michael Zanetti]

From the data sheet (http://www.datasheetspdf.com/PDF/MT6582/785907/11):

After that PWRKEYcan be released, pulling BBWAKEUP high will also turn
on the handset. This is the case when the alarm in the RTC expires.

So it seems the hardware should support to turn the device on when an
RTC alarm happens.

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

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

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

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

  This causes alarms to be lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1420169/+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 1447332] [NEW] alarms sceduled within the current minute trigger immediately

[Michael Zanetti]

Public bug reported:

Use case: a countdown timer.

As an app might be suspended by the time the countdown hits 0, currently
the alarm api is the only way to create such apps. However, for that use
case there would be a requirement for second-precision at least.

Currently, when a countdown is set to some few seconds, staying within
the current minute, the alarm will trigger immediately when it is synced
to the datetime-indicator, instead of waiting for the time to trigger.

If the alarm is longer, passing the next minute, it seems to actually
trigger it on the right time.

Here's an countdown app for testing that sets a countdown to 20 secs
from now: lp:~mzanetti/+junk/stopwatch-countdown

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

** Description changed:

  Use case: a countdown timer.
  
  As an app might be suspended by the time the countdown hits 0, currently
  the alarm api is the only way to create such apps. However, for that use
  case there would be a requirement for second-precision at least.
  
+ Currently, when a countdown is set to some few seconds, the alarm will
+ trigger immediately when it is synced to the datetime-indicator, instead
+ of waiting for the time to trigger.
+ 
+ If the alarm is longer, passing the next minute, it seems to actually
+ trigger it on the right time.
+ 
  Here's an countdown app for testing that sets a countdown to 20 secs
  from now: lp:~mzanetti/+junk/stopwatch-countdown

** Summary changed:

- alarms have minute-precision only, should be seconds
+ alarms sceduled within the current minute trigger immediately

** Description changed:

  Use case: a countdown timer.
  
  As an app might be suspended by the time the countdown hits 0, currently
  the alarm api is the only way to create such apps. However, for that use
  case there would be a requirement for second-precision at least.
  
- Currently, when a countdown is set to some few seconds, the alarm will
- trigger immediately when it is synced to the datetime-indicator, instead
- of waiting for the time to trigger.
+ Currently, when a countdown is set to some few seconds, staying within
+ the current minute, the alarm will trigger immediately when it is synced
+ to the datetime-indicator, instead of waiting for the time to trigger.
  
  If the alarm is longer, passing the next minute, it seems to actually
  trigger it on the right time.
  
  Here's an countdown app for testing that sets a countdown to 20 secs
  from now: lp:~mzanetti/+junk/stopwatch-countdown

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

Title:
  alarms sceduled within the current minute trigger immediately

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Use case: a countdown timer.

  As an app might be suspended by the time the countdown hits 0,
  currently the alarm api is the only way to create such apps. However,
  for that use case there would be a requirement for second-precision at
  least.

  Currently, when a countdown is set to some few seconds, staying within
  the current minute, the alarm will trigger immediately when it is
  synced to the datetime-indicator, instead of waiting for the time to
  trigger.

  If the alarm is longer, passing the next minute, it seems to actually
  trigger it on the right time.

  Here's an countdown app for testing that sets a countdown to 20 secs
  from now: lp:~mzanetti/+junk/stopwatch-countdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1447332/+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] [NEW] snoozing an alarm causes time to freeze

[Michael Zanetti]

Public bug reported:

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.

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

** Attachment added: clock.png
   https://bugs.launchpad.net/bugs/1435736/+attachment/4354330/+files/clock.png

-- 
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:
  snoozing an alarm causes time to freeze

Status in indicator-datetime package in Ubuntu:
  New

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/ubuntu/+source/indicator-datetime/+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 1431384] Re: Need a mechanism for specifying an ical event's icon

[Michael Zanetti]

** Changed in: indicator-datetime (Ubuntu)
   Status: Triaged = Confirmed

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

Title:
  Need a mechanism for specifying an ical event's icon

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This issue was raised in discussion with mzanetti, who would like
  reminders (created with reminder-app) to be shown in the drop-down
  menu with that app's icon.

  datetime currently is implemented with everything is either a clock-
  app alarm or a calendar-app event, which is not an approach that will
  scale to 3rd party apps. I suggest we add something like an x-unity-
  alarm-icon tag to the ical components to let clients specify their own
  icon as a string that gets passed to unity8.

  See related bug https://bugs.launchpad.net/ubuntu/+source/indicator-
  datetime/+bug/1426519 for letting the clients, rather than datetime,
  specify the behavior when the menuitems are clicked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1431384/+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 1420169] Re: Alarms don't set RTC alarm to wake up the phone

[Michael Zanetti]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03.03.2015 03:01, Charles Kerr wrote:
 Is the request here to power on the phone even if the user has
 manually powered it off?

Yes bug more importantly, if the phone has switched itself off because
of low battery.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlT1emkACgkQXJwWsxE5x7h9PwCfYL4w9/7wpwdIYMduFvHBN6cc
TloAn0SbaITh7XFDbTehEHCjCyQwIXe1
=13ls
-END PGP SIGNATURE-


** Changed in: indicator-datetime (Ubuntu)
   Status: Incomplete = 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/1420169

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

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

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

  This causes alarms to be lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1420169/+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 1411643] [NEW] Automatic brightness toggle switch missing on krillin/vivid

[Michael Zanetti]

Public bug reported:

I noticed that on my krillin device with devel-propsed (r70), the
automatic display brightness toggle switch is missing in the battery
indicator.

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  Automatic brightness toggle switch missing on krillin/vivid

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  I noticed that on my krillin device with devel-propsed (r70), the
  automatic display brightness toggle switch is missing in the battery
  indicator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1300649] Re: Schemas should not come with the library package

[Michael Zanetti]

schemas moved to unity-schemas, and unity8 has been updated to depend on
that instead of libunity-core

** Changed in: unity
   Status: Confirmed = Fix Released

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

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

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

Title:
  Schemas should not come with the library package

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  ⟫ dpkg -L libunity-core-6.0-9 | grep schemas
  /usr/share/glib-2.0/schemas
  /usr/share/glib-2.0/schemas/com.canonical.Unity.gschema.xml
  /usr/share/glib-2.0/schemas/org.compiz.unityshell.gschema.xml
  /usr/share/glib-2.0/schemas/org.compiz.unitymtgrabhandles.gschema.xml
  /usr/share/glib-2.0/schemas/org.compiz.unitydialog.gschema.xml
  /usr/share/glib-2.0/schemas/org.compiz.networkarearegion.gschema.xml

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:30:16 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1300649/+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 1300650] Re: Should use separate schema for launcher items

[Michael Zanetti]

** No longer affects: unity

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

Title:
  Should use separate schema for launcher items

Status in The Sevilerow project:
  New
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Won't Fix
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  We're using the schema from unity for launcher items, but we should
  instead use a custom one, since unity7 will never support click
  packages, so they're not compatible already.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140327.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14-0ubuntu1
  Architecture: armhf
  Date: Tue Apr  1 09:30:11 2014
  InstallationDate: Installed on 2014-04-01 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140401)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/sevilerow/+bug/1300650/+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 1378817] Re: apparmor denial for /home/phablet/.local/share/applications/ and /usr/share/applications/

[Michael Zanetti]

I have reduced the main.cpp to this:


int main(int argc, char *argv[])
{
QGuiApplication a(argc, argv);
return a.exec();
}


and I still get those warnings. I guess something in QApplication is checking 
out the install paths. Shouldn't be a real problem.

** Changed in: tagger
   Status: New = Opinion

** Changed in: reminders-app
   Status: New = Opinion

** Changed in: tagger
 Assignee: (unassigned) = Michael Zanetti (mzanetti)

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

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

Title:
  apparmor denial for /home/phablet/.local/share/applications/ and
  /usr/share/applications/

Status in Ubuntu Reminders app:
  Opinion
Status in Tagger:
  Opinion
Status in “qtbase-opensource-src” package in Ubuntu:
  New
Status in “url-dispatcher” package in Ubuntu:
  New

Bug description:
  Reminders and tagger are for some reason trying to do a read on
  /home/phablet/.local/share/applications/ and /usr/share/applications/,
  but apparmor policy disallows this:

  apparmor=DENIED operation=open 
profile=com.ubuntu.developer.mzanetti.tagger_tagger_0.5.1.0 
name=/home/phablet/.local/share/applications/ pid=NNN comm=tagger 
requested_mask=r denied_mask=r fsuid=32011 ouid=32011
  apparmor=DENIED operation=open 
profile=com.ubuntu.developer.mzanetti.tagger_tagger_0.5.1.0 
name=/usr/share/applications/ pid=NNN comm=tagger requested_mask=r 
denied_mask=r fsuid=32011 ouid=0
  apparmor=DENIED operation=open 
profile=com.ubuntu.reminders_reminders_0.5.262 
name=/home/phablet/.local/share/applications/ pid=NNN comm=reminders 
requested_mask=r denied_mask=r fsuid=32011 ouid=32011
  apparmor=DENIED operation=open 
profile=com.ubuntu.reminders_reminders_0.5.262 
name=/usr/share/applications/ pid=NNN comm=reminders requested_mask=r 
denied_mask=r fsuid=32011 ouid=0

  This is disallowed because allowed them would constitute a privacy
  leak. I'm not sure why these apps are doing it and not others-- I
  would guess they are trying to see if an application is installed so
  it can use it instead of using url dispatcher. Adding qtbase-
  opensource-src and url-dispatcher tasks, but feel free to adjust.

  Not marking for RTM and marking as medium since the applications seem
  to otherwise function ok and this is just noise in the logs on a
  couple of applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/reminders-app/+bug/1378817/+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: Forward button does not work

[Michael Zanetti]

Oh, this is actually in the media player app itself. Afaik it does
playlist handling on its own instead of using the media hub's playlist
capabilities, also doesn't implement mpris on its own, so it doesn't
work.

-- 
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:
  Forward button does not work

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

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 1368101] Re: Stopped apps don't restart when launched from another app

[Michael Zanetti]

** Summary changed:

- Suspended apps don't restart when launched from another app
+ Stopped apps don't restart when launched from another app

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) = Gerry Boland (gerboland)

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

Title:
  Stopped apps don't restart when launched from another app

Status in Qt integration with the Mir display server:
  New
Status in “qtmir” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New
Status in “url-dispatcher” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:-

  1) Open twitter webapp and sign in
  2) Open browser
  3) Open some other apps to ensure browser gets cleaned up by app lifecycle
  4) Switch to twitter
  5) Click on a link in a tweet

  Expected behaviour:-

  * Clicked link opens in browser

  Actual behaviour:-

  * Nothing

  
  Note, you can swipe back to browser to wake it up from suspend, then back 
to twitter, click the link and it _will_ switch back to browser and open the 
link.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1368101/+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 1300650] Re: Should use separate schema for launcher items

[Michael Zanetti]

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

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

Title:
  Should use separate schema for launcher items

Status in The Sevilerow project:
  New
Status in Unity:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Won't Fix
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  We're using the schema from unity for launcher items, but we should
  instead use a custom one, since unity7 will never support click
  packages, so they're not compatible already.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140327.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14-0ubuntu1
  Architecture: armhf
  Date: Tue Apr  1 09:30:11 2014
  InstallationDate: Installed on 2014-04-01 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140401)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/sevilerow/+bug/1300650/+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 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode

[Michael Zanetti]

** Attachment added: Tiny mouse cursor above panel
   
https://bugs.launchpad.net/unity/+bug/1359211/+attachment/4189052/+files/on-panel.png

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

Title:
  Mouse cursor tiny when hovering unity elements in high DPI mode

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  On a high DPI screen (220 DPI) the mouse cursor is really tiny when
  hovering unity elements. There are various keys in dconf to change the
  cursor's scale factor or size. I've managed to change it in a way that
  it looks normal when inside application windows, but its still tiny
  when on unity elements.

  I think this should be set automatically by the scale factor setting
  in system settings.

  
  (Using unity 7.3.1+14.10.20140811-0ubuntu1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1359211/+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 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode

[Michael Zanetti]

** Attachment added: Normal cursor over thunderbird
   
https://bugs.launchpad.net/unity/+bug/1359211/+attachment/4189070/+files/Workspace%201_007.png

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

Title:
  Mouse cursor tiny when hovering unity elements in high DPI mode

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  On a high DPI screen (220 DPI) the mouse cursor is really tiny when
  hovering unity elements. There are various keys in dconf to change the
  cursor's scale factor or size. I've managed to change it in a way that
  it looks normal when inside application windows, but its still tiny
  when on unity elements.

  I think this should be set automatically by the scale factor setting
  in system settings.

  
  (Using unity 7.3.1+14.10.20140811-0ubuntu1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1359211/+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 1328646] Re: Clock out of sync on resume from suspend

[Michael Zanetti]

Being away for a while and not having the phone plugged in all the time
this happened to me too all the time. But the panel seems to lag behind
too. It's in sync, but outdated. The time only updates when the next
minute update is triggered which in worst case leaves you with an
outdated clock for 59 seconds.

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  New
Status in The Unity 8 shell:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1236292] Re: Using volume buttons on phone triggers spurious popup

[Michael Zanetti]

** Tags added: doesnt-need-test

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

Title:
  Using volume buttons on phone triggers spurious popup

Status in Sound Menu:
  Fix Released
Status in The Unity 8 shell:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released

Bug description:
  Flashed mako with image #82. Press volume rocker, get a popup with no
  image and just the text 'indicator-sound'. See screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1236292/+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 1231444] Re: Use /// to remove hostname element

[Michael Zanetti]

** Tags added: doesnt-need-test

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

Title:
  Use /// to remove hostname element

Status in Bluetooth Menu:
  Fix Released
Status in The Date and Time Indicator:
  Fix Released
Status in Indicator Location:
  Fix Released
Status in Network Menu:
  Fix Released
Status in The Power Indicator:
  Fix Released
Status in Sound Menu:
  Fix Released
Status in The Unity 8 shell:
  Fix Released
Status in URL Dispatcher:
  Fix Released
Status in “indicator-bluetooth” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “url-dispatcher” package in Ubuntu:
  Fix Released

Bug description:
  
  The standard URL format (summarized) is $(protocol)://$(hostname)/$(stuff).  
Since most of the custom URLs we're using have no hostname, and QtUrl treats it 
specially, we need to ensure that it's not an issue.  URL dispatcher was not 
enforcing this on some URLs, and needs to be adjusted to enforce.  Others 
weren't specified that way, and they need to be changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1231444/+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 1223635] Re: Move Title to Backend

[Michael Zanetti]

** Tags added: has-test

-- 
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, dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1223635

Title:
  Move Title to Backend

Status in Bluetooth Menu:
  Fix Released
Status in The Date and Time Indicator:
  Fix Released
Status in Indicator Location:
  Fix Released
Status in The Messaging Menu:
  Fix Released
Status in Network Menu:
  Fix Released
Status in The Power Indicator:
  Fix Released
Status in Sound Menu:
  Fix Released
Status in The Sevilerow project:
  New
Status in The Unity 8 shell:
  Fix Released
Status in “indicator-bluetooth” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  We should have the titles in the root action state for the indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1223635/+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 1236249] Re: unity8 crashed with SIGSEGV in UnityMenuModelPrivate::itemState()

[Michael Zanetti]

** Tags added: has-test

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

Title:
  unity8 crashed with SIGSEGV in UnityMenuModelPrivate::itemState()

Status in Bluetooth Menu:
  Fix Released
Status in “indicator-bluetooth” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “indicator-bluetooth” source package in Saucy:
  Fix Released
Status in “ubuntu-system-settings” source package in Saucy:
  Fix Released
Status in “unity8” source package in Saucy:
  Fix Released

Bug description:
  TEST CASE:
  1. Open BT indicator and disable BT
  2. Open system-settings
  3. Select BT
  4. Enable/Disable BT several times (max 2 or 3)
  = indicator doesn’t appear and eventually u-s-s and unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity8 7.82+13.10.20131005-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: armhf
  CrashCounter: 1
  Date: Mon Oct  7 09:15:09 2013
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1380974656
  InstallationDate: Installed on 2013-10-05 (1 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20131005)
  MarkForUpload: True
  ProcCmdline: unity8
  ProcCwd: /home/phablet
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   ?? ()
   UnityMenuModelPrivate::itemState(_GtkMenuTrackerItem*) () from 
/usr/lib/arm-linux-gnueabihf/libqmenumodel.so.0
   UnityMenuModel::data(QModelIndex const, int) const () from 
/usr/lib/arm-linux-gnueabihf/libqmenumodel.so.0
   UnityMenuModel::get(int, QByteArray const) () from 
/usr/lib/arm-linux-gnueabihf/libqmenumodel.so.0
   RootActionState::updateActionState() () from 
/usr/lib/arm-linux-gnueabihf/unity8/qml/Unity/Indicators/libIndicatorsQml.so
  Title: unity8 crashed with SIGSEGV in UnityMenuModelPrivate::itemState()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty 
video

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1236249/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch

[Michael Zanetti]

** Tags added: needs-ap-test

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

Title:
  uevent spam causes libdbus client code in session upstart to consume
  massive amounts of memory on Ubuntu Touch

Status in Upstart:
  New
Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  In Progress
Status in “linux” source package in Saucy:
  Invalid
Status in “systemd” source package in Saucy:
  Invalid
Status in “unity” source package in Saucy:
  New
Status in “upstart” source package in Saucy:
  Fix Released

Bug description:
  using ubuntu touch image 82 i see the session init consume about 10MB per 
minute as long as the screen is on  with Mir.
  running the same session with surfaceflinger only consumes 1MB per minute.

  in both cases the system starts to swap heavily at some point, making
  the UI unresponsive.

  http://paste.ubuntu.com/6196223/ has the top output of a Mir session
  after 30min, the UI just got completely unresponsive when this
  snapshot was taken.

  http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger
  session where the screen was off for about 10min

  apparently the leak only occurs while the screen is on, it seems to be
  permanently there but in the case of surfaceflinger it hits less hard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1235649/+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