Accessible description doesn't update in 14.04

Bug #1079784 reported by Mathieu Trudel-Lapierre on 2012-11-16
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-power
New
Medium
Charles Kerr
indicator-power (Ubuntu)
Medium
Unassigned

Bug Description

Compare to bug 891932.

While running tests for indicator-power, an error pops up for a missing accessible description:

(process:14724): libindicator-WARNING **: IndicatorObject class does not have an accessible description.

While running IndicatorTest.GObjectNew and IndicatorTest.NoDevices.

I think this should be investigated. Could just be a false positive, but we really should have accessible descriptions for everything if possible.

Changed in indicator-power:
importance: Undecided → Medium
assignee: nobody → Charles Kerr (charlesk)
Charles Kerr (charlesk) on 2012-11-16
Changed in indicator-power:
milestone: none → 13.04.0
Luke Yelavich (themuso) wrote :

The poewr indicator does have an accessible description as of 14.04, however it is not updated according to the change in power state. The accessible description update signal needs to be emitted. Since the changes made in the indicator stack, I no longer know what the signal is called.

Charles Kerr (charlesk) on 2014-05-30
Changed in indicator-power (Ubuntu):
importance: Undecided → Medium
summary: - Missing accessible description
+ Accessible description doesn't update in 14.04
Changed in indicator-power:
milestone: 13.04.0 → none
Charles Kerr (charlesk) wrote :

Luke, so the accessible description starts off in sync with the icon, but falls out of sync as the battery state updates over time?

On Fri, May 30, 2014 at 09:18:40AM CEST, Charles Kerr wrote:
> Luke, so the accessible description starts off in sync with the icon,
> but falls out of sync as the battery state updates over time?

Correct. An easier way to reproduce is to disconnect/connect a power supply. In either case, reviewing the indicator on the panel with Orca produces the same string of text. At the moment I am told that I have 3 hours and 55 minutes left on my battery, even though I am plugged in.

Luke

Nic (nhschleicher) wrote :

I'm running into this same problem. doing a pkill -f indicator-power-source will get it reporting the correct value again, but I'd rather not have to implement a workaround.

Charlie Jonshon (charlie164) wrote :

I was facing the face problem then I visited https://oniton.com/blog/windows-10-startup-folder-not-working/ and after that I got the appropriate solution to resolve this problem.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers