[Dx-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level

[Charles Kerr]

** Changed in: indicator-power (Ubuntu)
 Assignee: Charles Kerr (charlesk) => (unassigned)

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

Title:
  Power indicator favours 'not present' mouse over laptop battery level

Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power source package in Xenial:
  New

Bug description:
  [Impact]

   * It's very annoying to see the mouse battery instead of the system
  battery on indicator bar.

  [Test Case]

   * Using Logitech Wireless Mouse M325 or other wireless mouse can see
  this issue.

  [Regression Potential]

   * No regression as I know.

  [Other Info]
   
   * This is a SRU request for Ubuntu 16.04 (xenial).

  The power indicator shows the battery level for cordless mice and
  keyboards, even when it cannot identify the battery level. This is a
  problem as it seems to favour showing a "not present" mouse status
  over the laptop battery level in the top bar.

  I haven't done a good job of explaining it, so check out the
  screenshot - it will explain all :)

  Basically, the laptop battery should be shown in the top bar if the 
mouse/keyboard is "not present".
  Also hiding the mouse and keyboard when the battery level is unknown would 
also be useful too :)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 17 10:11:16 2013
  InstallationDate: Installed on 2012-12-14 (33 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214)
  MarkForUpload: True
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1100546/+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 1674389] Re: Session Indicator's "Suspend" button has no effect in Unity 8

[Charles Kerr]

Might be a two-parter bug.

On the indicator-session side, we need to handle "challenge" as a
response to CanSuspend / CanHibernate calls and, when calling
suspend/hibernate, allow interactivity. This is in the fix-suspend-on-u8
branch.

Even after this is done, u8's challenge prompt is the lockscreen, so the 
unintuitive UX is that you have to (appear to) unlock in order to suspend. So 
in u8,
1. we should consider whether a password prompt should be necessary for 
suspend, and
2. if prompt is necessary, Calls to login1.Suspend(interactive=True) should 
probably be handled more elegantly than showing the lockscreen prompt


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

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

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

Title:
  Session Indicator's "Suspend" button has no effect in Unity 8

Status in indicator-session package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing Unity 8 from a Zesty nightly iso install on March 17 2017.

  When clicking on the "Suspend" button in the session indicator,
  nothing happens.

  This may or may not be an indicator-session issue. I need to triage
  this and see where the breakage is, e.g. does it work in Unity 7 on
  Zesty, and are there are any DBus signatures that have changed in
  Zesty that would cause this

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1674389/+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 1674389] [NEW] Session Indicator's "Suspend" button has no effect in Unity 8

[Charles Kerr]

Public bug reported:

Testing Unity 8 from a Zesty nightly iso install on March 17 2017.

When clicking on the "Suspend" button in the session indicator, nothing
happens.

This may or may not be an indicator-session issue. I need to triage this
and see where the breakage is, e.g. does it work in Unity 7 on Zesty,
and are there are any DBus signatures that have changed in Zesty that
would cause this

** Affects: indicator-session (Ubuntu)
 Importance: Undecided
 Assignee: Charles Kerr (charlesk)
 Status: Confirmed

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

Title:
  Session Indicator's "Suspend" button has no effect in Unity 8

Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  Testing Unity 8 from a Zesty nightly iso install on March 17 2017.

  When clicking on the "Suspend" button in the session indicator,
  nothing happens.

  This may or may not be an indicator-session issue. I need to triage
  this and see where the breakage is, e.g. does it work in Unity 7 on
  Zesty, and are there are any DBus signatures that have changed in
  Zesty that would cause this

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1674389/+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 on several devices

[Charles Kerr]

Reopening for workitem found by dobey to see if
https://code.launchpad.net/~morphis/indicator-bluetooth/fix-
lp1530807/+merge/290022 should still be landed

** Changed in: indicator-bluetooth (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: indicator-bluetooth (Ubuntu)
 Assignee: Charles Kerr (charlesk) => Rodney Dawes (dobey)

-- 
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 on several devices

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in indicator-bluetooth package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

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/avila/+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 1642989] [NEW] indicators should use 'com.canonical.indicators.link' type for Settings links

[Charles Kerr]

Public bug reported:

http://bazaar.launchpad.net/~unity-
team/unity8/trunk/view/head:/qml/Panel/Indicators/MenuItemFactory.qml
has this code:

> if (modelData.action !== undefined && modelData.action.indexOf("settings") > 
> -1) {
>   // FIXME : At the moment, the indicators aren't using
>   // com.canonical.indicators.link for settings menu. Need to fudge it.
>   return linkMenu;
> }

We should set the type of settings menuitems to
'com.canonical.indicators.link' so that this hack can be removed.

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

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

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

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

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

** Affects: indicator-session (Ubuntu)
 Importance: Medium
 Status: Triaged

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

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

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

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

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

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

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

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

Title:
  indicators should use 'com.canonical.indicators.link' type for
  Settings links

Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  Triaged
Status in indicator-sound package in Ubuntu:
  New

Bug description:
  http://bazaar.launchpad.net/~unity-
  team/unity8/trunk/view/head:/qml/Panel/Indicators/MenuItemFactory.qml
  has this code:

  > if (modelData.action !== undefined && modelData.action.indexOf("settings") 
> -1) {
  >   // FIXME : At the moment, the indicators aren't using
  >   // com.canonical.indicators.link for settings menu. Need to fudge it.
  >   return linkMenu;
  > }

  We should set the type of settings menuitems to
  'com.canonical.indicators.link' so that this hack can be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1642989/+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 1638716] Re: Hardcoded path in recoverable-problem may cause problems in Snappy

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-session/lp-1638716-recoverable-
whoopsie

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

Title:
  Hardcoded  path in recoverable-problem may cause problems in Snappy

Status in indicator-session package in Ubuntu:
  Triaged

Bug description:
  As described by mterry in 

  > And I left the "/usr/share/apport/recoverable_problem" hardcoded path in
  > src/recoverable-problem.c. That seems like more of a deb-based reporting
  > tool anyway. And I wasn't sure there is some plan for snappy to include
  > an error reporting tool or what.

  I suspect we don't need this recoverable error anymore in indicator-
  session, so we could remove it. If we do still need it, we need to see
  if this approach needs any modification in the snappy world

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638716/+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 1638716] Re: Hardcoded path in recoverable-problem needs evaluation for Snappy

[Charles Kerr]

Happily recoverable errors are handled in libwhoopsie, so indicator-
session can farm out that work.

Similar normalization patch in UAL:
https://code.launchpad.net/~ted/ubuntu-app-launch/recoverable-whoopsie/+merge/310212

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

** Summary changed:

- Hardcoded  path in recoverable-problem needs evaluation for Snappy
+ Hardcoded  path in recoverable-problem may cause problems in Snappy

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

Title:
  Hardcoded  path in recoverable-problem may cause problems in Snappy

Status in indicator-session package in Ubuntu:
  Triaged

Bug description:
  As described by mterry in 

  > And I left the "/usr/share/apport/recoverable_problem" hardcoded path in
  > src/recoverable-problem.c. That seems like more of a deb-based reporting
  > tool anyway. And I wasn't sure there is some plan for snappy to include
  > an error reporting tool or what.

  I suspect we don't need this recoverable error anymore in indicator-
  session, so we could remove it. If we do still need it, we need to see
  if this approach needs any modification in the snappy world

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638716/+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 1611466] Re: Calendar crashes on ESC typing.

[Charles Kerr]

I'm marking this bug as closed due to your last comment on no longer
being able to reproduce it, either through an update or some other
reason. If the problem reappears for you in the future, please submit a
backtrace using the method linked to by seb128 in the comment above.
Thank you again for taking the time to report this bug and helping to
make Ubuntu better. Please submit any future bugs you may find.

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

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

Title:
  Calendar crashes on ESC typing.

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  When you click on date, it opens the calendar, if you type the ESC
  button on keyboard, the graphical interface crashes and in a few
  seconds it restart. During this few seconds or a minute, all the
  system stay frozen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1611466/+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 1639472] Re: Alarm should provide GAction for toggling them

[Charles Kerr]

Marco, could you explain more what you're asking for here? A way to
toggle on/off whether alarms will go off?

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

Title:
  Alarm should provide GAction for toggling them

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Indicator-datetime should provide a GAaction for toggling the
  activation of alarms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1639472/+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 1638708] Re: Hardcoded paths in data/*.desktop.in need Snappy prefixing

[Charles Kerr]

** Description changed:

- Noticed and reported by mterry in https://code.launchpad.net/~mterry
- /indicator-sound/snap-root/+merge/308125:
+ Noticed and reported by mterry in several indicator patches, e.g.
+ :
  
  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.

** Summary changed:

- Hardcoded paths in data/*.desktop.in need Snappy prefixing
+ Hardcoded paths in desktop files need to be processed need $SNAP prefixing

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

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

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

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

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

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

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

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

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

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

** Description changed:

  Noticed and reported by mterry in several indicator patches, e.g.
  :
  
  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.
+ 
+ There is also an umbrella ticket for hardcoded paths in the u8 snap:
+ 

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

Title:
  Hardcoded paths in desktop files need to be processed need $SNAP
  prefixing

Status in indicator-application package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-printers package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  New

Bug description:
  Noticed and reported by mterry in several indicator patches, e.g.
  :

  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1638708/+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 1638716] Re: Hardcoded path in recoverable-problem needs evaluation for Snappy

[Charles Kerr]

** Description changed:

  As described by mterry in 
  
  > And I left the "/usr/share/apport/recoverable_problem" hardcoded path in
  > src/recoverable-problem.c. That seems like more of a deb-based reporting
  > tool anyway. And I wasn't sure there is some plan for snappy to include
  > an error reporting tool or what.
  
  I suspect we don't need this recoverable error anymore in indicator-
  session, so we could remove it. If we do still need it, we need to see
  if this approach needs any modification in the snappy world
+ 
+ There is also an umbrella ticket for hardcoded paths in the u8 snap:
+ 

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

Title:
  Hardcoded  path in recoverable-problem needs evaluation for Snappy

Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  As described by mterry in 

  > And I left the "/usr/share/apport/recoverable_problem" hardcoded path in
  > src/recoverable-problem.c. That seems like more of a deb-based reporting
  > tool anyway. And I wasn't sure there is some plan for snappy to include
  > an error reporting tool or what.

  I suspect we don't need this recoverable error anymore in indicator-
  session, so we could remove it. If we do still need it, we need to see
  if this approach needs any modification in the snappy world

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638716/+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 1638721] Re: Hardcoded paths need to work inside Snappy

[Charles Kerr]

** Description changed:

  As reported by mterry in his $SNAP exec patch
  :
  
  > The com.ubuntu.touch.AccountsService.Sound.xml file
  > has hardcoded paths to a couple sound files.
  >
  > ALARM_DEFAULT_SOUND and CALENDAR_DEFAULT_SOUND
  > are replaced in many files. Some data (gschema)
  > and some code. The code instances can easily be
  > changed to prefix $SNAP. The data files would
  > need a rethink.
+ 
+ There is also an umbrella ticket for hardcoded paths in the u8 snap:
+ 

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

Title:
  Hardcoded paths need to work inside Snappy

Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  As reported by mterry in his $SNAP exec patch
  :

  > The com.ubuntu.touch.AccountsService.Sound.xml file
  > has hardcoded paths to a couple sound files.
  >
  > ALARM_DEFAULT_SOUND and CALENDAR_DEFAULT_SOUND
  > are replaced in many files. Some data (gschema)
  > and some code. The code instances can easily be
  > changed to prefix $SNAP. The data files would
  > need a rethink.

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638721/+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 1638710] Re: Hardcoded paths need Snappy prefixing

[Charles Kerr]

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

D'oh, user error. This is the same as bug #1638708

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

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

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

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

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

** Tags removed: unity8-snap

** This bug has been marked a duplicate of bug 1638708
   Hardcoded paths in desktop files need to be processed need $SNAP prefixing

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

Title:
  Hardcoded paths need Snappy prefixing

Status in indicator-session package in Ubuntu:
  New

Bug description:
  Noticed and reported by mterry in https://code.launchpad.net/~mterry
  /indicator-transfer/snap-root/+merge/308128:

  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  >
  > I'm not sure what the best solution for those is, but presumably
  > it would lie in whichever component consumes the desktop file
  > not this package.

  As mterry points out this is probably not an issue for indicator-
  transfer to fix, this ticket is being filed so that we track the issue
  & see if there's anything that can be done locally or to reassign to
  proper owner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638710/+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 1638721] [NEW] Hardcoded paths need to work inside Snappy

[Charles Kerr]

Public bug reported:

As reported by mterry in his $SNAP exec patch
:

> The com.ubuntu.touch.AccountsService.Sound.xml file
> has hardcoded paths to a couple sound files.
>
> ALARM_DEFAULT_SOUND and CALENDAR_DEFAULT_SOUND
> are replaced in many files. Some data (gschema)
> and some code. The code instances can easily be
> changed to prefix $SNAP. The data files would
> need a rethink.

There is also an umbrella ticket for hardcoded paths in the u8 snap:


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


** Tags: unity8-snap

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

Title:
  Hardcoded paths need to work inside Snappy

Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  As reported by mterry in his $SNAP exec patch
  :

  > The com.ubuntu.touch.AccountsService.Sound.xml file
  > has hardcoded paths to a couple sound files.
  >
  > ALARM_DEFAULT_SOUND and CALENDAR_DEFAULT_SOUND
  > are replaced in many files. Some data (gschema)
  > and some code. The code instances can easily be
  > changed to prefix $SNAP. The data files would
  > need a rethink.

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638721/+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 1638716] [NEW] Hardcoded path in recoverable-problem needs evaluation for Snappy

[Charles Kerr]

Public bug reported:

As described by mterry in 

> And I left the "/usr/share/apport/recoverable_problem" hardcoded path in
> src/recoverable-problem.c. That seems like more of a deb-based reporting
> tool anyway. And I wasn't sure there is some plan for snappy to include
> an error reporting tool or what.

I suspect we don't need this recoverable error anymore in indicator-
session, so we could remove it. If we do still need it, we need to see
if this approach needs any modification in the snappy world

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


** Tags: unity8-snap

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

Title:
  Hardcoded  path in recoverable-problem needs evaluation for Snappy

Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  As described by mterry in 

  > And I left the "/usr/share/apport/recoverable_problem" hardcoded path in
  > src/recoverable-problem.c. That seems like more of a deb-based reporting
  > tool anyway. And I wasn't sure there is some plan for snappy to include
  > an error reporting tool or what.

  I suspect we don't need this recoverable error anymore in indicator-
  session, so we could remove it. If we do still need it, we need to see
  if this approach needs any modification in the snappy world

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638716/+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 1638710] [NEW] Hardcoded paths need Snappy prefixing

[Charles Kerr]

Public bug reported:

Noticed and reported by mterry in https://code.launchpad.net/~mterry
/indicator-transfer/snap-root/+merge/308128:

> There are also two hardcoded paths in the data/*.desktop.in files.
> But that's a static desktop file, so $SNAP isn't appropriate.
>
> I'm not sure what the best solution for those is, but presumably
> it would lie in whichever component consumes the desktop file
> not this package.

As mterry points out this is probably not an issue for indicator-
transfer to fix, this ticket is being filed so that we track the issue &
see if there's anything that can be done locally or to reassign to
proper owner

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

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


** Tags: unity8-snap

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

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

Title:
  Hardcoded paths need Snappy prefixing

Status in indicator-session package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  Confirmed

Bug description:
  Noticed and reported by mterry in https://code.launchpad.net/~mterry
  /indicator-transfer/snap-root/+merge/308128:

  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  >
  > I'm not sure what the best solution for those is, but presumably
  > it would lie in whichever component consumes the desktop file
  > not this package.

  As mterry points out this is probably not an issue for indicator-
  transfer to fix, this ticket is being filed so that we track the issue
  & see if there's anything that can be done locally or to reassign to
  proper owner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638710/+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 1633319] Re: memory leak in indicator-datetime

[Charles Kerr]

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

>From Jonathan's insights in comment 9, this sounds like a duplicate of
bug #1342123.

** This bug has been marked a duplicate of bug 1342123
   evolution-calendar-factory always running with high memory usage

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1634059] Re: indicator-datetime-service devours memory rendering system useless

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1633319
   memory leak in indicator-datetime
** This bug has been marked a duplicate of bug 1342123
   evolution-calendar-factory always running with high memory usage

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

Title:
  indicator-datetime-service devours memory rendering system useless

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Upon upgrading to 16.10, yakkety yak, I cannot load Unity because the
  indicator-datetime-service devours memory at an incredible pace before
  being automatically killed, and restarting to devour all over again!

  The workaround I found is to open a virtual terminal 
  and then log into unity while quickly switching back to the the F1
  terminal.  I then repeatedly do "killall -KILL indicator-datetime-
  service" until it stops coming back.

  This is a major bug in that it renders the entire system unusable.  It
  happened on both my laptop and my desktop after upgrade to 16.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 17 11:02:54 2016
  InstallationDate: Installed on 2014-10-13 (735 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1634059/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked

[Charles Kerr]

After looking through the code, Pat's thoughts in comment 14 seem right
to me.

For indicator-datetime's part, it can pass the system bus into the
object constructor instead of making an asynchronous call to fetch it.
This narrows the dangerous interval in datetime between wakeup and
calling requestSysState -- though, NB, I'm not able to reproduce this
bug in testing and so I'm not able to determine how much this change
ameliorates it.

Outside of indicator-datetime, this might be a question for repowerd wrt
ensuring that, after system wakeup, apps have a chance to respond to the
wakeup before the system goes back to sleep.

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1588526-remember-
system-bus

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1554504] Re: Calendar reminder does not wake phone when airplane mode is enabled

[Charles Kerr]

Pat, yes we use the com.canonical.powerd interface's requestWakeup
method to wakeup the phone when a clock alarm or calendar event needs a
notification.

indicator-datetime doesn't have any airplane mode logic in it at all, so
I'm not sure what's going on there.

I'm not able to reproduce this on a n4 running 15.04 (r531) by turning
on airplane mode and trying calendar events and a clock-app alarm. Is
this issue reproducible for anyone?

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

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

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

Title:
  Calendar reminder does not wake phone when airplane mode is enabled

Status in Canonical System Image:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  If airplane mode is enabled, the phone seems to go into a deep sleep
  where it doesn't wake up for a calendar reminder. The reminder does
  not sound until the power button is pressed to wake the phone, in some
  cases this has been more than an hour after the reminder was scheduled
  for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554504/+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 1384354] Re: Should ellipsize events names

[Charles Kerr]

This should be handled in the rendering, rather than in the strings we
pass across the bus to Unity

** Package changed: indicator-datetime (Ubuntu) => unity8 (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/1384354

Title:
  Should ellipsize events names

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using utopic, if you calendar contains an event with a long name the
  indicator menu is stretched to contain it which looks weird,
  ellipsizing those would be nice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1384354/+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 1626275] Re: Date for Daylight Saving Time end appears two times in the indicator

[Charles Kerr]

Lukas, could you take a look at this?

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

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

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

Title:
  Date for Daylight Saving Time end appears two times in the indicator

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

Bug description:
  bq e4.5 OTA-13 and bq M10 rc-proposed
  This year the Daylight Saving Time ends on 30th October in UK. That day 
appears twice in the indicator. See the screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626275/+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 1622682] [NEW] incorrect use of 'summary' event property in popup notifications

[Charles Kerr]

Public bug reported:

As described in RFC 2445:

> When the action is "DISPLAY", the alarm MUST also include a
"DESCRIPTION" property, which contains the text to be displayed when the
alarm is triggered.

The ingest code in engine-eds.cpp is correctly reading the `description'
property to initialize the Alarm struct's 'text' field, but then when it
comes time to display the alarm, it uses Appointment.summary instead.

This appears to be a code leftover from the time before indicator-
datetime added multiple valarm support by separating the Alarm and
Appointment structures.

** Affects: indicator-datetime (Ubuntu)
 Importance: Medium
 Assignee: Charles Kerr (charlesk)
 Status: In Progress

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

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- should use vevent 'description' property in notifications
+ incorrect use of 'summary' event property in popup notifications

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

Title:
  incorrect use of 'summary' event property in popup notifications

Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  As described in RFC 2445:

  > When the action is "DISPLAY", the alarm MUST also include a
  "DESCRIPTION" property, which contains the text to be displayed when
  the alarm is triggered.

  The ingest code in engine-eds.cpp is correctly reading the
  `description' property to initialize the Alarm struct's 'text' field,
  but then when it comes time to display the alarm, it uses
  Appointment.summary instead.

  This appears to be a code leftover from the time before indicator-
  datetime added multiple valarm support by separating the Alarm and
  Appointment structures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1622682/+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 1388931] Re: [clock] No setting for 12h or 24h clock format any more

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  [clock] No setting for 12h or 24h clock format any more

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Clock App:
  Won't Fix
Status in Ubuntu UX:
  Won't Fix
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Before the new design, the clock app had a setting for 12h or 24h (bug
  1268158). With the new design, that is now gone, and there is no way
  to get a 24h clock, when using a locale that defaults to 12h.

  This should probably be a setting in the Time & Date settings control
  panel, rather than in the clock itself, but I'm filing it in both
  places, as previously setting the format in the clock did not affect
  the format in the rest of the system (as such a setting should do).

  gsetting  com.canonical.indicator.datetime time-format controls this

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388931/+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 1523698] Re: indicator-session is leaking memory on ubuntu 15.10

[Charles Kerr]

Matthew, please report the separate unity-settings-daemon issue to
 so
that it can be tracked there.

Regarding the glib parse_value_from_blob() reported above, it looks like
the upstream fix mentioned by seb128 is in 16.04. Is anyone still seeing
indicator-session leak memory in >= 16.04?

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

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

Title:
  indicator-session is leaking memory on ubuntu 15.10

Status in indicator-session package in Ubuntu:
  Incomplete

Bug description:
  The `indicator-session-service` is slowly leaking memory, after a
  while it has used up over 10 gigabytes of RAM and swap and the entire
  system freezes.

  I've reinstalled the entire OS, and even started using a new home
  folder, but it's still happening.

  indicator-session:
Geïnstalleerd: 12.10.5+15.10.20150915-0ubuntu1
Kandidaat: 12.10.5+15.10.20150915-0ubuntu1
Versietabel:
   *** 12.10.5+15.10.20150915-0ubuntu1 0
  500 http://be.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1523698/+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 1470080] Re: Broken icon in indicator when iphone attached

[Charles Kerr]

Yep. In addition to the fixes above, we should also fall back to foo-bar
when foo-bar-charging is unavailable.

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

Title:
  Broken icon in indicator when iphone attached

Status in indicator-power package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Running wily with an iPhone 4 (but I doubt it matters which rev of
  iphone) attached, I see a combined battery gauge for desktop and phone
  in the indicator. Unfortunately the icon is broken / missing when the
  phone is attached, like it's missing a small version of the icon you
  see in system settings -> power.

  See screenshot (next to 61%)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20150522-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 30 12:10:40 2015
  InstallationDate: Installed on 2014-06-16 (379 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2015-05-09 (51 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1470080/+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 1470080] Re: Broken icon in indicator when iphone attached

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-power/lp-1470080-missing-icon-
when-apple-devices-connected

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

Title:
  Broken icon in indicator when iphone attached

Status in indicator-power package in Ubuntu:
  Triaged

Bug description:
  Running wily with an iPhone 4 (but I doubt it matters which rev of
  iphone) attached, I see a combined battery gauge for desktop and phone
  in the indicator. Unfortunately the icon is broken / missing when the
  phone is attached, like it's missing a small version of the icon you
  see in system settings -> power.

  See screenshot (next to 61%)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20150522-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 30 12:10:40 2015
  InstallationDate: Installed on 2014-06-16 (379 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2015-05-09 (51 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1470080/+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 1581089] Re: Clock app opened when closing Alarms

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1581089-dont-open-
clock-app-when-dismissing-alarms

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

Title:
  Clock app opened when closing Alarms

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Recently, when my alarm goes off in the morning, and I tap the OK
  button to close it, that when I later unlock my phone for the first
  time, the clock app is opened. The clock app should not be opened
  whenever I cancel an alarm.

  This is on rc-proposed on hammerhead (Nexus 5), but I don't see any
  reason this would be device specific.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581089/+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 1581089] Re: Clock app opened when closing Alarms

[Charles Kerr]

Confirmed, I'm seeing this in ubuntu-touch/rc-proposed/bq-aquaris.en
build r332.

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

Title:
  Clock app opened when closing Alarms

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Recently, when my alarm goes off in the morning, and I tap the OK
  button to close it, that when I later unlock my phone for the first
  time, the clock app is opened. The clock app should not be opened
  whenever I cancel an alarm.

  This is on rc-proposed on hammerhead (Nexus 5), but I don't see any
  reason this would be device specific.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581089/+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 1538760] Re: battery icon gone

[Charles Kerr]

Hm ok, it looks like indicator-power's icon is gone because indicator-
power-service isn't running.

1. Is there anything for indicator-power in /var/crash?

2. What happens if you run "$ start indicator-power" ?

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

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

Title:
  battery icon gone

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  Usually the power/battery indicator works as expected.
  However, now I turned on my laptop while not connected to AC power, and there 
is no battery icon at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 27 22:10:15 2016
  InstallationDate: Installed on 2013-10-11 (838 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+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 841220] Re: Session returns to login screen when attemping to shutdown or restart

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 838792
   "Restart" logs out, even when there are no other people logged in
** This bug has been marked a duplicate of bug 1242112
   Shutdown/restart dialogue is not working if Cairo-Dock and its 
Launcher-API-Deamon are running or if another app is registered to 
LauncherEntry interface of Unity DBus

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

Title:
  Session returns to login screen when attemping to shutdown or restart

Status in indicator-session package in Ubuntu:
  New

Bug description:
  When choosing shutdown or restart the session just returns me to the login 
screen.
  If I choose to shutdown from the login screen nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: indicator-session 0.3.4.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic-pae 3.0.4
  Uname: Linux 3.0.0-10-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Sun Sep  4 19:05:11 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/841220/+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 1538760] Re: battery icon gone

[Charles Kerr]

teo, could you please attach the output of this command the next time
the icon disappears:

$ dbus-send --print-reply=literal --dest=com.canonical.indicator.power
/com/canonical/indicator/power org.gtk.Actions.DescribeAll

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

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

Title:
  battery icon gone

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  Usually the power/battery indicator works as expected.
  However, now I turned on my laptop while not connected to AC power, and there 
is no battery icon at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 27 22:10:15 2016
  InstallationDate: Installed on 2013-10-11 (838 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+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 1559731] Re: Battery indicator turns red at 30%

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-power/lp-1559731-fix-red-
battery-icon-at-29pct-on-desktop

** Changed in: indicator-power (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Battery indicator turns red at 30%

Status in indicator-power package in Ubuntu:
  In Progress
Status in indicator-power source package in Xenial:
  Triaged

Bug description:
  The indicator turns red as soon as battery goes 30%

  Please refer to the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-power 12.10.6+16.04.20160105-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 20 20:43:32 2016
  InstallationDate: Installed on 2016-03-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1559731/+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: [indicators] Battery icon turns red at 30%

[Charles Kerr]

See also bug #1559731

-- 
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:
  [indicators] Battery icon turns red at 30%

Status in Canonical System Image:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu RTM:
  Fix Released

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/canonical-devices-system-image/+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 1559731] Re: Battery indicator turns red at 30%

[Charles Kerr]

This looks like a Desktop variation of bug #1388235. The solution there
was to provide extra icons for 10%, 30%, 50%, 70%, and 90% so that we
could improve our accuracy when rounding to the closest icon, and also
to special case the rounding between [20-30%) to avoid hitting the red-
at-20% icons from not just our own icon sets but others eg Humanity.

I'm seeing the same behavior on my Xenial box when I set the battery to
28%.  The icon list sent by indicator-power is correct:

> {"battery-030", "gpm-battery-030", "battery-020", "gpm-battery-020",
"battery-low-symbolic", "battery-low"}

So the rounding rules described in bullet point #2 of
https://bugs.launchpad.net/ubuntu/+source/indicator-
power/+bug/1388235/comments/5 are working correctly and things look
great on devices with suru icons. The problem for the Desktop is that
bullet point #3 is incorrect:

> indicator-power keep providing the current icon names as fallbacks so
that this fix doesn't break compatibility with other icon themes

Because ?keeping the current icon names as fallbacks" means the problem
still persists in other icon sets. We should tweak the special case rule
for [20-30%) s.t. the fallback icon is *040* instead of *020*, e.g.:

-  {"battery-030", "gpm-battery-030", "battery-020", "gpm-battery-020", 
"battery-low-symbolic", "battery-low"}
+ {"battery-030", "gpm-battery-030", "battery-040", "gpm-battery-040", 
"battery-low-symbolic", "battery-low"}


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

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

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

Title:
  Battery indicator turns red at 30%

Status in indicator-power package in Ubuntu:
  Triaged
Status in indicator-power source package in Xenial:
  Triaged

Bug description:
  The indicator turns red as soon as battery goes 30%

  Please refer to the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-power 12.10.6+16.04.20160105-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 20 20:43:32 2016
  InstallationDate: Installed on 2016-03-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1559731/+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 1569593] Re: Doesn't include auto-detected timezone even if the setting is enabled

[Charles Kerr]

Still WfM. seb128, any suggestions on how to reproduce this issue?

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

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

Title:
  Doesn't include auto-detected timezone even if the setting is enabled

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  Using Xenial, the indicator doesn't seem to include the locale
  locations even if the "Time in auto-detected location” is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1569593/+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 1567516] Re: The default indicators set has a blank button.

[Charles Kerr]

** Package changed: indicator-application (Ubuntu) => indicator-keyboard
(Ubuntu)

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

Title:
  The default indicators set has a blank button.

Status in indicator-keyboard package in Ubuntu:
  New

Bug description:
  The default indicators set has a blank button. when I click on that button, 
it drops down to 3 options, character map, keyboard layout chart, text entry 
settings.
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-03-12 (26 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  Package: indicator-application 12.10.1+15.04.20150128-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Tags: xenial third-party-packages
  Uname: Linux 4.4.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-14 (13 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  Package: indicator-application 12.10.1+15.04.20150128-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Tags: xenial third-party-packages
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin mail plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1567516/+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 1575612] Re: indicator-power-service crashed with SIGSEGV in g_object_unref()

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
your system at the time of the report. Please upgrade your system to the
latest package versions. If you still encounter the crash, please file a
new report.

Thank you for your understanding, and sorry for the inconvenience!

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

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

Title:
  indicator-power-service crashed with SIGSEGV in g_object_unref()

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  Crash after login.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue Apr 26 20:04:37 2016
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service
  InstallationDate: Installed on 2015-06-16 (315 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service
  SegvAnalysis:
   Segfault happened at: 0x7f88c4917c1c :mov
(%rdi),%rax
   PC (0x7f88c4917c1c) ok
   source "(%rdi)" (0x0021) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-power
  StacktraceTop:
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-power-service crashed with SIGSEGV in g_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  mtime.conffile..etc.xdg.autostart.indicator.power.desktop: 
2015-06-17T00:28:16.335589

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1575612/+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 1575293] Re: Remove the non-existing "systemd-services" dependency

[Charles Kerr]

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

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

Title:
  Remove the non-existing "systemd-services" dependency

Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  Trying to upgrade systemd 229-5 but wants to remove indicator-session.

  Looking at its dependencies, one is now missing since 'trusty' : 
systemd-services
  http://packages.ubuntu.com/trusty-updates/systemd-services
  http://packages.ubuntu.com/yakkety/systemd-services

  Looks like that dependency has been re-introduced, which should not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-session 12.10.5+16.04.20160412-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 20:06:25 2016
  SourcePackage: indicator-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1575293/+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 1362962] Re: Calendar icon usually shows the wrong date

[Charles Kerr]

tiheum, \o/

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

Title:
  Calendar icon usually shows the wrong date

Status in Canonical System Image:
  In Progress
Status in Ubuntu Calendar App:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Fix Committed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Problem occurs with: Ubuntu 14.10 r203
  Does not occur with: iOS, Windows Phone

  1. In the clock menu, find the calendar app and launch it.
  2. In the Launcher or Dash, find the Calendar app.

  What you see:
  1. The icon always says "25", regardless of the actual date.
  2. The icon always says "28", regardless of the actual date.

  What you should see:
  1. The icon shows the current date.
  2. The icon shows the current date.

  The equivalent for PC is bug 1362033, and for the Clock app is bug
  1362964.

  This depends on bug 1453795 for Unity letting an app change its own
  icon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362962/+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: [FHD] Bluetooth cannot be activated on several devices

[Charles Kerr]

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

-- 
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:
  [FHD] Bluetooth cannot be activated on several devices

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

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/avila/+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 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5

[Charles Kerr]

Reassigning to powerd. Indicator-power gets the min/max brightness range
from powerd by calling com.canonical.powerd's getBrightnessParams()
method.

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

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

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

Title:
  Possible to manually set display brightness to 0 on Ubuntu Touch on
  Aquaris E5

Status in indicator-power package in Ubuntu:
  Invalid
Status in powerd package in Ubuntu:
  New

Bug description:
  Possible to manually set display brightness to 0 on Ubuntu Touch

  It is possible to move the brightness slider to the very left
  position, which will set the display brightness of affected device to
  zero, or, to total darkness.

  This is a bug, since this leads to user's inability to set the brightness 
back or, generally, to operate the device.
  There is a slight chance, though, to return the brightness back to non-zero 
value (blindly, trying by user's memory).

  Also, this gets even more problematic, if we think about a scenario, where 
such Ubuntu device is locked by a PIN.
  User has to try to unlock the device on the dark screen, open the top panel 
with settings, scroll to the far right (to access the brightness settings), and 
then trying to hit the correct slider - all on a dark screen.

  This happened on Aquaris E5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+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 1569593] Re: Doesn't include auto-detected timezone even if the setting is enabled

[Charles Kerr]

I'm not able to reproduce this issue when testing at the hotel in
Prague.  seb128 reports it WfH here too, so perhaps the error is
conditional on location or network.

Will try again on my layovers on the way back to test different
locations / timezones / networks.

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

Title:
  Doesn't include auto-detected timezone even if the setting is enabled

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Using Xenial, the indicator doesn't seem to include the locale
  locations even if the "Time in auto-detected location” is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1569593/+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 1560960] Re: test-live-actions frequently hangs on powerpc on xenial

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  test-live-actions frequently hangs on powerpc on xenial

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  An example build that timed out:

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-013/+build/6180155

  It happened three times on both powerpc and ppc64el over the last
  hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-datetime 15.10+16.04.20160310-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 13:37:33 2016
  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/1560960/+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 1570948] Re: [Alarm] "Now" not localized in indicator datetime

[Charles Kerr]

indicator-datetime intentionally doesn't format that string. Instead, it
sends a time_t to unity so that unity can update the string periodically
without indicator-datetime generating more bus traffic.

The time_t is pulled in by alarmMenu and appointmentMenu in
qml/Panel/Indicators/MenuItemFactory.qml, which then formats the string
using i18n.relativeDateTime() which is implemented in ubunut-ui-toolkit
at src/Ubuntu/Components/plugin/i18n.cpp's
UbuntuI18n::relativeDateTime(), though it appears to be marked for
translation there:

>case DATE_PROXIMITY_NOW:
>/* TRANSLATORS: Time based "this is happening/happened now" */
>return dtr("ubuntu-ui-toolkit", "Now");


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

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

** Changed in: indicator-datetime (Ubuntu)
   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/1570948

Title:
  [Alarm] "Now" not localized in indicator datetime

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

Bug description:
  Test case.
  - Switch the phone to Spanish.
  - Open clock app.
  - Create an alarm for the next minute.
  - Open indicator time.

  Expected result.
  - "Alarm: Now" must be translated to Spanish.

  Actual result.
  - "Now" is not localized.

  I can't find the string in Launchpad.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1570948/+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 1567940] Re: time displayed wrongly on production phone

[Charles Kerr]

So, I wrote a simple script to test my branch by looping through
rebooting the phone and asking indicator-datetime what time it thought
it was.

* Wednesday's runs: 'automatic' time setting with London specified as
the tzid

* Thursday's runs: 'manual' time setting (as inspired by Ren's comment
#8) with America/Los_Angeles specified as the tzid

1000+ reboots later,  I checked the outputs to see if they always
increased over time or if there were outliers that jumped to the wrong
timezone. The output looked like this:

>  variant  string " 7:40 AM"
>  variant  string " 7:42 AM"
>  variant  string " 7:43 AM"
>  variant  string " 7:44 AM"
>  variant  string " 7:45 AM"
>  variant  string " 7:47 AM"
>  variant  string " 7:48 AM"

For these two cases, at least, It looks like this branch is working.

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

Title:
  time displayed wrongly on production phone

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  My phone displays the time an hour out on the lockscreen and notification 
bar. It is a production BQ 4.5 phone, and I am using it in the UK where 
Canonical are based, so this isn't a weird edge case situation at all. I have 
reflashed it altogether, and upgraded yesterday to OTA-10. It has a read only 
filesystem.
  If I go to time and date, and try to change my timezone it shows 
Europe/London UTC+1 and below it shows the correct time ticking away with BST 
at the end of it.
  If I try to change the timezone I get the daft list of cities, selecting them 
now highlights them in blue rather than orange, but I can't choose any of them. 
I have zero clue where there might be any indication of an error log to look 
for.

  
  http://people.ubuntu.com/~alanbell/phone/timezone.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567940/+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 1567940] Re: time displayed wrongly on production phone

[Charles Kerr]

Alan, if my guess in comment 5 is correct, it's a timing issue that will
show up only occasionally after booting, depending on how soon
indicator-datetime starts making bus calls compared to when some bus
services are ready. Some code in the indicator was making bus calls on
startup rather than looking for a bus owner to be ready and /then/
making the bus calls.

That doesn't explain the cities-in-blue-rather-than-orange issue in
system settings though. Possibly two bugs for the price of one?

** Also affects: ubuntu-system-settings (Ubuntu)
   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/1567940

Title:
  time displayed wrongly on production phone

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  My phone displays the time an hour out on the lockscreen and notification 
bar. It is a production BQ 4.5 phone, and I am using it in the UK where 
Canonical are based, so this isn't a weird edge case situation at all. I have 
reflashed it altogether, and upgraded yesterday to OTA-10. It has a read only 
filesystem.
  If I go to time and date, and try to change my timezone it shows 
Europe/London UTC+1 and below it shows the correct time ticking away with BST 
at the end of it.
  If I try to change the timezone I get the daft list of cities, selecting them 
now highlights them in blue rather than orange, but I can't choose any of them. 
I have zero clue where there might be any indication of an error log to look 
for.

  
  http://people.ubuntu.com/~alanbell/phone/timezone.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567940/+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 1568963] [NEW] option to disable 'low battery' sound

[Charles Kerr]

Public bug reported:

Mentioned by Victor Gabillon in the ubuntu-phone mailing list:

> I was wondering if there was an option to disable/enable
> the sound notification that warns you about the low level
> of the battery. I find this sound sometimes very annoying.
> For instance while sleeping or when you are actually
> charging it but the (bad quality) cable disconnects/
> reconnect randomly and triggers the sound every
> single time.

Adding this is easy enough, at a minimum as a 'hidden' gsettings schema
flag that could be poked from the command line.

It's up to Design whether this is something to expose in system-
settings.

** Affects: indicator-power (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: indicator-power (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  option to disable 'low battery' sound

Status in indicator-power package in Ubuntu:
  New

Bug description:
  Mentioned by Victor Gabillon in the ubuntu-phone mailing list:

  > I was wondering if there was an option to disable/enable
  > the sound notification that warns you about the low level
  > of the battery. I find this sound sometimes very annoying.
  > For instance while sleeping or when you are actually
  > charging it but the (bad quality) cable disconnects/
  > reconnect randomly and triggers the sound every
  > single time.

  Adding this is easy enough, at a minimum as a 'hidden' gsettings
  schema flag that could be poked from the command line.

  It's up to Design whether this is something to expose in system-
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1568963/+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 1560960] Re: test-live-actions frequently hangs on powerpc on xenial

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

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

** Branch linked: lp:~charlesk/indicator-datetime/lp-1560960-use-
dbusmock-timedated-template

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

Title:
  test-live-actions frequently hangs on powerpc on xenial

Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  An example build that timed out:

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-013/+build/6180155

  It happened three times on both powerpc and ppc64el over the last
  hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-datetime 15.10+16.04.20160310-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 13:37:33 2016
  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/1560960/+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 1567940] Re: time displayed wrongly on production phone

[Charles Kerr]

Looking over the indicator-datetime code I do see a startup timing bug
that might be causing this and have a patch for that; however, I'm not
able to reproduce this bug on my krillin. Under the 'startup timing bug'
working theory I've tried rebooting 10x and still am not seeing this
bug.

I'll get the patch reviewed and put it in a silo so that other people
experiencing this bug can see if it helps their phones.

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

Title:
  time displayed wrongly on production phone

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

Bug description:
  My phone displays the time an hour out on the lockscreen and notification 
bar. It is a production BQ 4.5 phone, and I am using it in the UK where 
Canonical are based, so this isn't a weird edge case situation at all. I have 
reflashed it altogether, and upgraded yesterday to OTA-10. It has a read only 
filesystem.
  If I go to time and date, and try to change my timezone it shows 
Europe/London UTC+1 and below it shows the correct time ticking away with BST 
at the end of it.
  If I try to change the timezone I get the daft list of cities, selecting them 
now highlights them in blue rather than orange, but I can't choose any of them. 
I have zero clue where there might be any indication of an error log to look 
for.

  
  http://people.ubuntu.com/~alanbell/phone/timezone.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567940/+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 1567940] Re: time displayed wrongly on production phone

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-datetime/always-get-initial-
tzid-from-timedate1

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

Title:
  time displayed wrongly on production phone

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

Bug description:
  My phone displays the time an hour out on the lockscreen and notification 
bar. It is a production BQ 4.5 phone, and I am using it in the UK where 
Canonical are based, so this isn't a weird edge case situation at all. I have 
reflashed it altogether, and upgraded yesterday to OTA-10. It has a read only 
filesystem.
  If I go to time and date, and try to change my timezone it shows 
Europe/London UTC+1 and below it shows the correct time ticking away with BST 
at the end of it.
  If I try to change the timezone I get the daft list of cities, selecting them 
now highlights them in blue rather than orange, but I can't choose any of them. 
I have zero clue where there might be any indication of an error log to look 
for.

  
  http://people.ubuntu.com/~alanbell/phone/timezone.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567940/+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 1566341] Re: ``Tomorrow'' appears untranslated

[Charles Kerr]

At very first glance, the code in indicator-datetime looks alright: the
string `Tomorrow' only occurs in utils.c's
generate_full_format_string_at_time(), all instances there are marked
for translation, and the only change to utils.c in the last year was a
comment change (http://bazaar.launchpad.net/~indicator-applet-developers
/indicator-datetime/trunk.15.10/revision/428).

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

Title:
  ``Tomorrow'' appears untranslated

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Reported in the ubuntu-phone mailing list's ``Landing team 31.03.16''
  thread:

  Richard Somlói:
  >  "Tomorrow" should be "Holnap" in Hungarian, and it worked well with the 
previous images. Could somebody confirm it with another language?

  sil2100:
  > I just checked the indicator-datetime language pack and see Tomorrow as 
translated in all possible places there, so at least it's not a problem with 
the langpack itself. I would recommend filling in a bug against 
indicator-datetime so that the developers can take a look what's wrong.
  > But there is certainly something wrong since I get the same issue with the 
Polish locale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1566341/+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 1566341] [NEW] ``Tomorrow'' appears untranslated

[Charles Kerr]

Public bug reported:

Reported in the ubuntu-phone mailing list's ``Landing team 31.03.16''
thread:

Richard Somlói:
>  "Tomorrow" should be "Holnap" in Hungarian, and it worked well with the 
> previous images. Could somebody confirm it with another language?

sil2100:
> I just checked the indicator-datetime language pack and see Tomorrow as 
> translated in all possible places there, so at least it's not a problem with 
> the langpack itself. I would recommend filling in a bug against 
> indicator-datetime so that the developers can take a look what's wrong.
> But there is certainly something wrong since I get the same issue with the 
> Polish locale.

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

** Attachment added: "screenshot of `Tomorrow' untranslated"
   
https://bugs.launchpad.net/bugs/1566341/+attachment/4624615/+files/tomorrow.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/1566341

Title:
  ``Tomorrow'' appears untranslated

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Reported in the ubuntu-phone mailing list's ``Landing team 31.03.16''
  thread:

  Richard Somlói:
  >  "Tomorrow" should be "Holnap" in Hungarian, and it worked well with the 
previous images. Could somebody confirm it with another language?

  sil2100:
  > I just checked the indicator-datetime language pack and see Tomorrow as 
translated in all possible places there, so at least it's not a problem with 
the langpack itself. I would recommend filling in a bug against 
indicator-datetime so that the developers can take a look what's wrong.
  > But there is certainly something wrong since I get the same issue with the 
Polish locale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1566341/+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 1325259] Re: Log out/Lock not functional with user with no password

[Charles Kerr]

I don't have a 14.04 setup to test with ATM, but trying the same in a
15.04 box, I can partially confirm this wrt the lockscreen, locking
doesn't work on a user with no password. The "lock/switch account..."
menuitem shouldn't be available in this case.

I'm not able to reproduce the Logout issue; logout works fine even on
accounts with no password. This needs re-testing on 14.04.

** Changed in: indicator-session (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Log out/Lock not functional with user with no password

Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  when creating a user account with no password, the lock and logout
  functions dont work. you must click on another users name to log out
  or lock the account. i think that the lock should take you back to the
  user selection screen without disrupting the windows in your account.
  the log out should sign out and discard your windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 31 16:00:45 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-30 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-05-30 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1325259/+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 1508438] Re: Do not notify for events marked as not attending

[Charles Kerr]

The thing to do here is to get some sample input from an imported
calendar with "not attending" set so that (a) this ical can be used as
the basis for a regression test and (b) we can see how to test for this
state in engine-eds.cc.

Once we have that test in place the rest of implementation is trivial,
just don't call add_alarms_to_subtask() for components that have "not
attending" set.

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

Title:
  Do not notify for events marked as not attending

Status in Ubuntu Calendar App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-up from bug #1371871. While it was marked as Fix
  Released, it doesn't seem to have had any effect. I'm reporting it as
  two separate bugs to reopen it now.

  I've got a few events in my calendar for meetings where I'm marked as
  not going, which I still want to see in my calendar unless I
  explicitly delete them.

  An example is a recurring event which I've got on my work calendar. During my 
holiday:
  - I'll mark myself as not attending
  - I will not delete the event
  - I don't expect to be notified

  As I'm not marked as attending, I wouldn't expect to get a reminder
  notification, even less if I'm in a different timezone and it's 3:00
  a.m. :)

  See bug 1508440 for the "display events not being attended clearly"
  part.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1508438/+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 1533681] Re: imported google calendar events sound when they shouldn't

[Charles Kerr]

Renato, thanks for working on some of the indicator-datetime backlog. =)

For this one, after the EDS engine collects all the alarms for an event,
it should cull out the ones that have neither an audio_url nor display
text, ie:

=== modified file 'src/engine-eds.cpp'
--- src/engine-eds.cpp  2016-02-03 16:33:39 +
+++ src/engine-eds.cpp  2016-03-29 17:53:12 +
@@ -960,7 +960,8 @@
 appointment.end = i.first.second;
 appointment.alarms.reserve(i.second.size());
 for (auto& j : i.second)
-appointment.alarms.push_back(j.second);
+if (!j.second.text.empty() || !j.second.audio_url.empty())
+appointment.alarms.push_back(j.second);
 subtask->task->appointments.push_back(appointment);
 }
 }

A few important notes:

1. I believe the clock app used to (and possibly still does?) write
empty valarms, so when testing this or any other fix you should confirm
that it doesn't break the clock. For backwards compatibility with
existing clock-app alarms, we may need indicator-datetime to inject an
Alarm if none is present for any event containing the "x-canonical-
alarm" tag.

2. Most of indicator-datetime's EDS tests were created with output from
clock-app, so new ical tests are needed to cover these other valarm
action types.

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

Title:
  imported google calendar events sound when they shouldn't

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Calendar App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I use the calendar-app with my work google calendar. For that calendar
  I have alarms setup to automatically send an email 24 hours, 4 hours
  and 30 minutes before any event and I choose email as the reminder (as
  opposed to popup) so that I wouldn't be bombarded with reminders all
  day. Unfortunately the calendar app does not make a distinction
  between email and popup and every event with an email reminder gets
  imported as an event that gets an event notification on the phone with
  an alarm sound. I have a lot of events in my calendar and so my phone
  is constantly making noise at all times of the day. This is
  particularly annoying at night time since I might get a reminder as
  early as 3am or 4am, which wakes me up. Of course, I could use silent
  mode at night, but, like last night, I forgot and was awoken at 6am.
  Plus, I don't necessarily want the phone in silent mode-- I'd like to
  be able to hear if a phone call comes in since that is likely an
  emergency call I need to take.

  There are a lot of different bugs related to calendar event
  notifications and if some of them were fixed, it would ameliorate this
  bug. For example, I've been hoping for a setting to disable sounds for
  just the calendar (whether via the app or system settings) but
  otherwise get calendar notifications. Being able to change the alarm
  sound to 'None' would work too. TBH at this point I don't care which
  bug is fixed, I need to get this phone to stop sounding off
  constantly.

  WORKAROUND:
  1. download https://commons.wikimedia.org/wiki/File:Silence.ogg to 
/home/phablet
  2. use gsettings to adjust the sound:
  $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime 
calendar-default-sound
  '/usr/share/sounds/ubuntu/ringtones/Marimbach.ogg'
  $ DISPLAY=:0.0 gsettings set com.canonical.indicator.datetime 
calendar-default-sound /home/phablet/Silence.ogg 
  $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime 
calendar-default-sound
  '/home/phablet/Silence.ogg'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533681/+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 1562898] Re: Yank effect in brightness bar

[Charles Kerr]

I'm seeing this too in rc-proposed r290 on bq.

** Changed in: indicator-power (Ubuntu)
   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/1562898

Title:
  Yank effect in brightness bar

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  When sliding left and right the brightness bar movement is not as
  smooth as it should, there is a yank effect. This has been seen in
  mako rc-proposed #402.

  This can be seen easily comparing how the bar moves when "Adjust
  brightness automatically" is set and when it is not.

  See also bug #1555215.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1562898/+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 1560960] Re: test-live-actions frequently hangs on powerpc on xenial

[Charles Kerr]

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

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  test-live-actions frequently hangs on powerpc on xenial

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  An example build that timed out:

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-013/+build/6180155

  It happened three times on both powerpc and ppc64el over the last
  hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-datetime 15.10+16.04.20160310-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 13:37:33 2016
  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/1560960/+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 1560188] Re: unity8 hang w/ CPU pegged

[Charles Kerr]

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => 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/1560188

Title:
  unity8 hang w/ CPU pegged

Status in Canonical System Image:
  In Progress
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

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

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

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

  More details are needed.

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

-- 
Mailing list: https://launchpad.net/~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 1560188] Re: unity8 hang w/ CPU pegged

[Charles Kerr]

Looks like this is being caused by the QML calendar widget: I can
consistently reproduce the freeze using ToyKeeper's recipe of
wipe+timezone+rotate on a freshly-flashed krillin running rc-proposed.
The freeze goes away for me after installing the linked branch from silo
70, which removes the calendar.

This is a u8 bug rather than an indicator-datetime one, but this is the
easiest place to back out the calendar for OTA10.

** Branch linked: lp:~charlesk/indicator-datetime/lp-1560188-remove-
calendar-from-phone-profile

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

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

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  unity8 hang w/ CPU pegged

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

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

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

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

  More details are needed.

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

-- 
Mailing list: https://launchpad.net/~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 676222] Re: With indicator-datetime calendar focused, cannot use arrow keys to navigate to other indicators

[Charles Kerr]

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

Title:
  With indicator-datetime calendar focused, cannot use arrow keys to
  navigate to other indicators

Status in One Hundred Papercuts:
  Invalid
Status in Indicator Display Objects:
  Triaged
Status in Indicator Date and Time:
  Triaged
Status in Unity Foundations:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid

Bug description:
  indicator-datetime 0.3.90-0ubuntu1, libido3-0.1-0 | 0.3.1-0ubuntu3,
  Ubuntu 12.04 beta 1 and earlier

  If whilst the date indicator is focused, you press the down keyboard
  arrow (and focus the calendar) then the left/right keyboard navigation
  breaks. The keyboard effectively gets "stuck" - there's no escape from
  the calendar.

  You cannot press the up arrow (which you might intuitively expect to
  undo the down arrow press).

  1. Open the clock menu.
  2. Press Down.
  3. Press Down.
  4. Press Up.
  5. Press Left.

  What happens:
  2. The date item is highlighted.
  3. Whichever date in the calendar was last highlighted in this Ubuntu session 
is highlighted.
  4. If that date was in the first week of the month, nothing. Otherwise, the 
previous week is highlighted.
  5. If that date was the first displayed, nothing. Otherwise, the previous 
date is highlighted.

  What should happen:
  2. The date item is highlighted.
  3. The month element in the calendar is highlighted.
  4. The date item is highlighted.
  5. The sound menu is opened.

  : "Up and Down
  should navigate to the previous and next weeks within the current
  month only; beyond the current month they should exit the grid."

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/676222/+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 1073403] Re: "Date format not supported"

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. When you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 

and any other logs that are relevant for this particular issue.

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

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

Title:
  "Date format not supported"

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  This is what is replaced with the clock. It says "Date format not
  supported". The only way I can get the clock back is if, under the
  clock tab, "Weekday" and "Date and month" are unchecked.

  http://www.freeimagehosting.net/oy641

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1073403/+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 1242307] Re: Doesn't report NTP connection problems

[Charles Kerr]

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

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

Title:
  Doesn't report NTP connection problems

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I'm using Ubuntu 13.04 64 bits. I have a problem with the indicator Date-Time.
  I'm using the option "Automatically from the Internet" to retrieve the hour 
for my system, it's works fine on my home network. But when I use a public 
network, this function doesn't work properly. It's due to the limited allowed 
ports I believe. So what are ports using in the indicator Date-Time for 
retrieving the hour?

  The most common port on a public network is just 80 (http port)

  PS: I'm using a public network all weeks, so that's important for me
  because I want to know sometime the hour..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1242307/+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

[Charles Kerr]

Do you mean 'off' as in literally turned off?

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

-- 
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 Ubuntu Clock App:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+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 1548479] Re: unity8 clock gui menu crashed

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the 
crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.


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

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

Title:
  unity8 clock gui menu crashed

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  opened unity8 kin terminal left clicked clock on gui and unity 8
  crashed.

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 16.04
  Package: indicator-datetime 15.10+16.04.20160129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  BadURL: appid://com.ubuntu.clock/clock/current-user-version
  CurrentDesktop: Unity
  Date: Mon Feb 22 13:25:44 2016
  DuplicateSignature: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service:url-dispatcher-bad-url
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2016-02-09 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  modified.conffile..etc.xdg.autostart.indicator.datetime.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.indicator.datetime.desktop: 
2016-02-10T20:02:56.836372

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1548479/+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 1170366] Re: Broken handling of All-Day events

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1302004-fix-event-
list-culling-and-sorting

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Broken handling of All-Day events

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  All-day events are not being shown on the day they occur, when that
  date is selected in the calendar, and all-day events which occur on
  Fridays seem to not be appearing at all. Furthermore, it also seems
  that all-day events which span multiple days are also handled poorly,
  listed as starting at 00:00 on the first day, and not appearing on the
  other days.

  In Online Services we have a few calendars for hours, meetings, and
  for the client engineering subteam we have review days, which we
  specify in a calendar. I have these calendars subscribed to in
  Evolution. The all-day events used to appear on the day they occurred,
  so this seems to be a regression.

  Some examples:

  All-day events; To see who is on call for reviews today, I must select
  the previous day. The event for Friday however, does not show up at
  all, so selecting Thursday dates on the calendar do not show me any
  future all-day events that occur on the Friday.

  Multi-day all-day event: I will be on holiday May 06-10, but this does
  not show correctly in the events list when I select any of those days.
  Instead, when I select the preceding Sunday May 05 in the calendar,
  the event shows as starting Monday at 00:00, rather than being an all-
  day event which spans multiple days.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu Apr 18 10:01:40 2013
  InstallationDate: Installed on 2012-10-21 (178 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to raring on 2012-12-24 (114 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1170366/+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 1317288] Re: Date and time do not show up on indicator panel

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. When you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 

and any other logs that are relevant for this particular issue.

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

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

Title:
  Date and time do not show up on indicator panel

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  Date-time indicator as well as a few other indicators (e.g. cpufreq,
  weather) do not show up on my indicator panel even though they are
  installed in my system.

  This happened for the first time after upgrading from Ubuntu 12.04 to
  14.04. It used to show up normaly before.

  Other indicators (e.g. keyboard, sound, multiload) show up normaly.

  I have tried different things like uninstalling and re-installing the
  missing indicators but no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed May  7 17:16:23 2014
  InstallationDate: Installed on 2011-01-13 (1210 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to trusty on 2014-04-30 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1317288/+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 1475081] Re: Alarm sounds during call

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Alarm sounds during call

Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  If you have set an alarm and you are on a call when the alarm is due
  to ring, it does ring out (through the speakers). You should get some
  kind of 'bleep' through the earpiece instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475081/+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 1302004] Re: Indicator-datetime doesn't list in-progress events

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1302004-fix-event-
list-culling-and-sorting

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

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

Status in indicator-datetime package in Ubuntu:
  In Progress

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

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

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

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1470583] Re: Phone notifies me of calendar events multiple times.

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
   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/1470583

Title:
  Phone notifies me of calendar events multiple times.

Status in Ubuntu Calendar App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in qtorganizer5-eds package in Ubuntu:
  Confirmed

Bug description:
  Open calendar
  Create a new event by tapping anywhere in the calendar timeline
  Tap Untitled new event to modify the time
  Set time to be a few moments from now
  Set reminder to be "On event"

  Time passes...

  Notification appears, sound rings at time of alarm

  2 minutes later

  Notification appears, sound rings

  .. and again..

  I'd expect it to only go off once.

  $ system-image-cli --info
  current build number: 54
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-07-01 10:51:36
  version version: 54
  version ubuntu: 20150701
  version device: 20150529-8e13c5f
  version custom: 20150528-722-29-15-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1470583/+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 756406] Re: there is no easy way to edit/include servers for NTP to sync from like it used to

[Charles Kerr]

** No longer affects: indicator-datetime

** Package changed: indicator-datetime (Ubuntu) => unity-control-center
(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/756406

Title:
  there is no easy way to edit/include servers for NTP to sync from like
  it used to

Status in Ayatana Design:
  New
Status in unity-control-center package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: ntp

  Up to Maverick, when I needed to adjust my NTP daemon where I wanted
  it to sync from, I could go to the Preferences/Date and time
  application and add or remove addresses from there (it would then
  reflect on my /etc/ntp.conf from then on) but now, there is no GUI for
  that... it simply lets me turn it on or off... the list, preset with
  pretty sane ntp providers, seemes OK, but one could want to sync to
  its local server, and had to go back to console and vim the conf file
  (not a issue for me, but... I believe it was a step back on Natty)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: ntp 1:4.2.6.p2+dfsg-1ubuntu5
  ProcVersionSignature: Ubuntu 2.6.38-8.41-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Sun Apr 10 06:23:57 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  KernLog:
   
  ProcEnviron:
   LANGUAGE=pt_BR:en
   LANG=en_US.UTF-8
   LC_MESSAGES=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-8.41-generic-pae 2.6.38.2
  SourcePackage: ntp
  UpgradeStatus: Upgraded to natty on 2011-04-10 (0 days ago)
  mtime.conffile..etc.ntp.conf: 2011-04-10T01:02:40.958183

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/756406/+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 735874] Re: Weekday and date missing from top panel indicator applet when in Classic Desktop mode

[Charles Kerr]

** No longer affects: indicator-datetime

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

Title:
  Weekday and date missing from top panel indicator applet when in
  Classic Desktop  mode

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  When using the Ubuntu Classic Desktop mode, the weekday and date are
  missing from the top panel indicator applet.

  This is the default "classic" configuration in Ubuntu 10.10, which is
  expected to be restored when using such mode in Ubuntu 11.04.

  It can be restored by left-clicking on the time, choosing "Time & Date
  Settings" and checking the "Weekday" and "Date & time" options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/735874/+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 1251599] Re: /usr/lib/x86_64-linux-gnu/indicator-datetime-service:6:_g_log_abort:g_assertion_message:g_assertion_message_expr:g_weak_ref_set:signal_closure_free

[Charles Kerr]

Thank you for reporting this bug to Ubuntu. 13.10 reached EOL on July 17, 2014.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases 

I've tried recreating this bug with your release and was unable to,
given the information you've provided. Please upgrade to the latest
version and re-test. If the bug is still reproducible, increase the
verbosity of the steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.

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

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

Title:
  /usr/lib/x86_64-linux-gnu/indicator-datetime-
  
service:6:_g_log_abort:g_assertion_message:g_assertion_message_expr:g_weak_ref_set:signal_closure_free

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-datetime.  This problem was most recently seen
  with version 13.10.0+13.10.20131023.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/f941e013da19489e12d4ccaa65d50fb833d06494
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1251599/+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 1324854] Re: indicator-datetime in saucy shows wrong time (& date) for some online calendars added in Evolution

[Charles Kerr]

Thank you for reporting this bug to Ubuntu. Saucy reached EOL on July
17, 2014.

We are sorry that we do not always have the capacity to look at all reported 
bugs in a timely manner. There have been many changes in Ubuntu since that time 
you reported the bug and your problem may have been fixed with some of the 
updates. It would help us a lot if you could test it on a currently supported 
Ubuntu version. When you test it and it is still an issue, kindly upload the 
updated logs by running only once:
apport-collect 

and any other logs that are relevant for this particular issue.

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

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

Title:
  indicator-datetime in saucy shows wrong time (& date) for some online
  calendars added in Evolution

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  After adding a online calendar in evolution (For example, Calendar
  Events from remember the milk), indicator-datetime
  (13.10.0+13.10.20131023.2-0ubuntu1.1) shows wrong date & time for the
  any event on that calendar even though it shows correct date & time in
  Evolution.

  My system timezone is Asia/Kolkata (GMT+5:30). Evolution is set to use
  system timezone. In remember the milk timezone is set for (GMT+5:30).
  However when I add it to evolution , indicator-datetime shows wrong
  date & time (exactly 5:30 hour ahead).Local eds calendar events or
  google calendars are not affected by this.This only  occurs for online
  calendars(webcal:\\) I have attached a screenshot.

  $ gsettings get com.canonical.indicator.datetime timezone-name
  '"Asia/Kolkata Kolkata"'

  $ cat rtm.ics | grep TZID
  TZID:Asia/Kolkata

  $ cat rtm.ics | grep X-WR-TIMEZONE
  X-WR-TIMEZONE:Asia/Kolkata

  $ cat rtm.ics | grep X-LIC-LOCATION
  X-LIC-LOCATION:Asia/Kolkata

  Here is the ical file I added to Evolution:
  http://paste.ubuntu.com/7550447/

  Test Case:
  ---
  1. Set remeber the milk timezone to your system timezone. Copy the ical 
address with events. The calendar must have events with time

  2. Add it to evolution.

  3. It appears ok in evolution.

  4. Restart indicator-datetime. Click on the clock menu & select the
  day of the event.

  The event will appear in wrong time (in my case, 5:30 hour ahead).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1324854/+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 1419391] Re: LANG=C environment breaks clock

[Charles Kerr]

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

Title:
  LANG=C environment breaks clock

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  When the environment contains LANG=C (in .pam_environment, for
  example), the clock in gnome-panel disapears if it is either in
  12-hour format, or it displays seconds.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-panel 1:3.8.0-1ubuntu12.2
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  8 14:06:58 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-panel
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-09-26 (134 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  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/1419391/+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 1424581] Re: indicator-datetime-service crashed with SIGSEGV in _int_malloc()

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. When you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 

and any other logs that are relevant for this particular issue.


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

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

Title:
  indicator-datetime-service crashed with SIGSEGV in _int_malloc()

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  I had to force a shutdown by cutting power off and then booting the
  computer, and then i got this crash report

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20141009-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb 23 11:29:57 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1412862947
  InstallationDate: Installed on 2014-10-16 (129 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /var/lib/lightdm
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f06ec58105e <_int_malloc+238>:  cmp
0x10(%rdx),%r12
   PC (0x7f06ec58105e) ok
   source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   _int_malloc (av=0x7f06ec8be760 , bytes=300) at malloc.c:3389
   __GI___libc_malloc (bytes=300) at malloc.c:2891
   __GI__IO_str_overflow (fp=0x7fff1b5f9de0, c=110) at strops.c:119
   __GI__IO_default_xsputn (f=0x7fff1b5f9de0, data=, n=34) at 
genops.c:480
   _IO_vfprintf_internal (s=s@entry=0x7fff1b5f9de0, format=, 
format@entry=0x7f06e35be9f0 
"type='signal',interface='ca.desrt.dconf.Writer',path='%s',arg0path='%s'", 
ap=ap@entry=0x7fff1b5f9f50) at vfprintf.c:1642
  Title: indicator-datetime-service crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to utopic on 2014-12-21 (63 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1424581/+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 1317945] Re: Clock indicator on panel is updating infreqently

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. When you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 

and any other logs that are relevant for this particular issue.


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

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

Title:
  Clock indicator on panel is updating infreqently

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  Recently I have noticed that my clock is frozen.  Clicking on the
  frozen time in the indicator shows the current time in the dropdown
  (below the calendar), however the displayed clock in the panel is
  never updated.

  Rebooting does not resolve the problem, but gives me an updated time
  displayed on the panel.

  It is probably unrelated, however earlier this week I did notice some
  skew (that I have never seen before), confirmed it was the system
  clock on the command line and ran an ntpdate-debian to update. I
  dismissed the skew as the result of suspending too many times without
  reboot during which I had also toggled different CPU schedulers and
  frequency to influence system performance.

  ntpdate-debian updated the time.  Likely a coincidence, but I have
  been noticing this clock issue since I had this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Fri May  9 10:45:08 2014
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1317945/+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 1548031] Re: wrong date in series schedule

[Charles Kerr]

Renato, have you had time to triage this yet -- do you know if the issue
is in calendar-app, or the indicator, or both?

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

Title:
  wrong date in series schedule

Status in Ubuntu Calendar App:
  Triaged
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Had the Problem that i have some series schedule, but the Alarm ring one 
month to early.
  see attach

  21.03.2016 is the schedule, but got today the alarm.

  Calendar App Version: 0.4.757

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1548031/+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 1557571] Re: Upcoming event ETA appears to fall out of sync

[Charles Kerr]

The "7 minutes til" text is coming from unity8.

indicator-datetime passes the event's time to unity8 in the x-canonical-
time property, and qml/Panel/Indicators/MenuItemFactory.qml's
appointmentMenu code builds its time from calling
i18n.relativeDateTime() on that x-canonical-time value.

Ideally, unity8 would have a timer kick at the top of the minute and
update appointmentMenu's time property.

A hackier solution would be for indicator-datetime to rebuild the menu
every minute. This should have the same effect for this ticket, but it
would involve unnecessary bus traffic and IMO doesn't address the
problem in the right place

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

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

** Changed in: ubuntu-calendar-app
   Status: New => Invalid

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

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

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

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

Title:
  Upcoming event ETA appears to fall out of sync

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Calendar App:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Triaged

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557571/+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 1330678] Re: indicator-datetime or -session missing ~10% of the time

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. When you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 

and any other logs that are relevant for this particular issue.


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

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

Title:
  indicator-datetime or -session missing ~10% of the time

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  Same symptoms as Bug #1239710  which was marked fixed. It happens
  quite frequently lately in my Ubuntu 14.04 install (fresh install).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun 16 23:03:32 2014
  InstallationDate: Installed on 2014-04-19 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  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/1330678/+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 1317861] Re: Alarm icon inappropriately shown for reminders too

[Charles Kerr]

This bug was fixed a long time ago but this ticket didn't get closed.
Marking as fix released.

** Changed in: indicator-datetime (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Alarm icon inappropriately shown for reminders too

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  The alarm indicator icon seems to be shown if you have any reminder
  set up, which basically means if you have any recurring event with a
  reminder, it will be shown constantly.

  I think the icon should only be shown when you have an alarm set up.

  The relevant design spec:
  https://wiki.ubuntu.com/TimeAndDate#Phone.2BAC8-tablet-1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  9 13:08:23 2014
  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/1317861/+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 1543206] Re: If there isn't a calendar, we should help the user install one

[Charles Kerr]

IIUC calendar-app is going to start shipping preinstalled on the phone.
If so, this issue would go away...

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

Title:
  If there isn't a calendar, we should help the user install one

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Currently the most reported bad URL for the URL dispatcher is clicking
  on the datetime indicator and not getting a calendar. Instead of doing
  that I think we should take the user to the store and suggest that
  they could find one. Basically, use this URL:

  scope://com.canonical.scopes.clickstore?q=name:com.ubuntu.calendar

  It isn't perfect, but I think better than not working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1543206/+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 1553696] Re: indicator-datetime-service crashed with SIGSEGV in g_type_check_instance()

[Charles Kerr]

** Information type changed from Private to Public

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_type_check_instance()

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  occurs on login

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: indicator-datetime 15.10+16.04.20160129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Mar  6 06:35:22 2016
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2016-02-23 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7eff737ead8d : mov
(%rdi),%rax
   PC (0x7eff737ead8d) ok
   source "(%rdi)" (0x72747365645f6c6c) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_handler_disconnect () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1553696/+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 741011] Re: Calendar in clock menu has inconsistent background color

[Charles Kerr]

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

** No longer affects: indicator-datetime

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

Title:
  Calendar in clock menu has inconsistent background color

Status in Indicator Display Objects:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Invalid

Bug description:
  indicator-datetime 0.1.98-0ubuntu1, Ubuntu Natty
  indicator-datetime 0.2.93-0ubuntu1, Ubuntu Ocelot

  1. In "Time & Date Settings…" > "Clock", check "Monthly calendar" if it is 
not checked already.
  2. Open the clock menu.

  What you see: The calendar has a different background color from the
  rest of the menu.

  What you should see: The calendar has exactly the same background
  color as the rest of the menu.

  (This report previously also mentioned a border around the calendar,
  which has since been fixed.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ido/+bug/741011/+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 740817] Re: Mousing over date in the menu's calendar doesn't highlight it

[Charles Kerr]

This is a rendering issue in IDO's code, not indicator-datetime.

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

Title:
  Mousing over date in the menu's calendar doesn't highlight it

Status in Indicator Display Objects:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: indicator-datetime

  indicator-datetime 0.1.98-0ubuntu1, Ubuntu Natty

  1. Open the clock menu.
  2. Mouse over any of the dates in the calendar.

  What happens: Nothing (apart from bug 740350).
  What should happen: The date under the mouse should highlight like a normal 
menu item.

  : "All dates
  shown in the calendar should behave, and look, as normal grid-layout
  menu items."

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

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Matthew Paul Thomas (mpt)

-- 
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 1362962] Re: Calendar icon usually shows the wrong date

[Charles Kerr]

indicator-datetime is already using the generic calendar icon from
ubuntu-mobile/actions/scalable/calendar.svg, which has the '25' in it.

IMO the issue is that the icon should be tweaked to remove the '25'

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Matthieu James (tiheum)

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

Title:
  Calendar icon usually shows the wrong date

Status in Ubuntu Calendar App:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Problem occurs with: Ubuntu 14.10 r203
  Does not occur with: iOS, Windows Phone

  1. In the clock menu, find the calendar app and launch it.
  2. In the Launcher or Dash, find the Calendar app.

  What you see:
  1. The icon always says "25", regardless of the actual date.
  2. The icon always says "28", regardless of the actual date.

  What you should see:
  1. The icon shows the current date.
  2. The icon shows the current date.

  The equivalent for PC is bug 1362033, and for the Clock app is bug
  1362964.

  This depends on bug 1453795 for Unity letting an app change its own
  icon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1362962/+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 1558492] Re: Confusing date icons for appointments listed in pulldown

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1362962
   Calendar icon usually shows the wrong date

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

Title:
  Confusing date icons for appointments listed in pulldown

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  The icons (see the red icons in the attached screenshot) next to the 
appointments are confusing or misleading, as they can easily be taken for the 
date of the appointment.
  Ideally they should contain the date (day in the month) of the appointment 
for a quick overview.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1558492/+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 1502684] Re: Enable Seconds on the Clock

[Charles Kerr]

The indicator's current behavior on the phone matches the design spec at
https://wiki.ubuntu.com/TimeAndDate#Phone.2Ftablet.

I'll be happy to update the code if design re-addresses this issue, eg
for convergence, but I'm not going to make an MP to go against the
design spec. :)

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

Title:
  Enable Seconds on the Clock

Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Invalid

Bug description:
  on Ubuntu touch when ever trying to set the clock to display seconds
  on the clock using gsettings, the value is getting updated but the
  clock is not showing the seconds.

  Following is the command that i used to enable seconds on the clock

  gsettings set com.canonical.indicator.datetime show-seconds true

  After this when i  check the value, it is showing true but the clock
  is not showing the seconds even after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1502684/+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 1558526] Re: Animation between months are not similar

[Charles Kerr]

** Package changed: indicator-datetime (Ubuntu) => unity8 (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/1558526

Title:
  Animation between months are not similar

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

Bug description:
  r274, rc-proposed, arale

  0. swipe from top edge (open indicator)
  1. be sure you are in time indicator, focus calendar
  2. swipe from middle of the calendar, from the right side (will show 
next/futur month)
  3. Watch the transition, the smooth animation. Do it 2-3 time to be sure you 
record it
  4. now scroll from middle of the calendar to the right (to show previous/past 
month)
  5. Wacth the transition,  looks like a tiny lag appears (if you don't release 
the finger to force a slow transition, you will notice that tiny lag appears 
when the "month - year " title above the calendar refreshs itself

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1558526/+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 1558492] Re: Confusing date icons for appointments listed in pulldown

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Confusing date icons for appointments listed in pulldown

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  The icons (see the red icons in the attached screenshot) next to the 
appointments are confusing or misleading, as they can easily be taken for the 
date of the appointment.
  Ideally they should contain the date (day in the month) of the appointment 
for a quick overview.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1558492/+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 1557571] [NEW] Upcoming event ETA appears to fall out of sync

[Charles Kerr]

Public bug reported:

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

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

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Assignee: Charles Kerr (charlesk)
 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/1557571

Title:
  Upcoming event ETA appears to fall out of sync

Status in indicator-datetime package in Ubuntu:
  New

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

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

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

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

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-bluetooth/lp-1530807-watch-
bluez-owner-on-bus

-- 
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 on several devices

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

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/avila/+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 1530807] Re: Bluetooth cannot be activated on several devices

[Charles Kerr]

I think there is an indicator-datetime issue herer wrt the on/off toggle
in the indicator, but there is also a separate issue with the
Discoverable / Not Discoverable status being shown in system-settings.
indicator-bluetooth doesn't advertise that state; system-settings is
getting that from talking to bluez.

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => Critical

-- 
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 on several devices

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

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/avila/+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 1474078] Re: Provide a way to disable notifications from calendar events

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1474078
-notification-blacklist-apps

** Branch unlinked: lp:~charlesk/indicator-datetime/lp-1474078-system-
settings-notification-blacklists

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

Title:
  Provide a way to disable notifications from calendar events

Status in Canonical System Image:
  In Progress
Status in Ubuntu Calendar App:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  While I like having the calendar on the phone I do not want an audible 
notification for the events. 
  Would we simply add the calendar app to the Notifications page?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1474078/+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] [NEW] Clicking a date in the new calendar doesn't change the indicator's appointment list

[Charles Kerr]

Public bug reported:

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.

** Affects: indicator-datetime (Ubuntu)
 Importance: Medium
 Assignee: Charles Kerr (charlesk)
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Medium
 Assignee: Lukáš Tinkl (lukas-kde)
 Status: New

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

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

** Description changed:

  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 
+ * 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 :-)
+ key-variant map GAction states.

-- 
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 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/+source/indicator-datetime/+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 1474078] Re: Provide a way to disable notifications from calendar events

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  Provide a way to disable notifications from calendar events

Status in Canonical System Image:
  In Progress
Status in Ubuntu Calendar App:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  While I like having the calendar on the phone I do not want an audible 
notification for the events. 
  Would we simply add the calendar app to the Notifications page?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1474078/+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 1532731] Re: Battery indicator still wrong on BQ Aquaris 4.5

[Charles Kerr]

For indicator-power's part, in this ticket it's giving the same
information that's passed to it by upower, so marking the indicator-
power component of this ticket as Invalid.

Adding Canonical System Image to the ticket for another pair of eyes.
I'm not able to reproduce this on my krillin and wonder if it might be a
hardware issue with that physical device

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

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

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

Title:
  Battery indicator still wrong on BQ Aquaris 4.5

Status in Canonical System Image:
  New
Status in indicator-power package in Ubuntu:
  Invalid

Bug description:
  The Battery indicator still works wrong on BQ Aquaris 4.5 with OTA
  8.5.

  The indicator claims that the remaining charge is X percent (lets say
  50%), but within minutes the phone switches off.

  OS: ATA-8.5
  Build: Ubuntu 15.04 - armhf (20151210-005527)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532731/+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 1515821] Re: Recurring Evolution events not shown as coming events in clock's menu

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  Recurring Evolution events not shown as coming events in clock's menu

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  In Evolution you can make an appointment recur according to a
  specified scheme. As from wily, only the first instance of such a
  recurring event is shown in the clock menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1515821/+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