Ticket #1425 (closed task: wontfix)

Opened 7 years ago

Last modified 4 years ago

Verify that camera activities close the camera device when not in use.

Reported by: jg Owned by: cjb
Priority: high Milestone: Future Release
Component: tinderbox Version:
Keywords: power Cc: bert, olpc-devel@…, mpg@…
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

The camera activity, Etoys, and any other camera activity should close the camera device when idle, or when they are not the visible activity on the screen.

This is to ensure no interference between activities, along with minimizing power usage.

Change History

Changed 7 years ago by erikb

  • cc olpc-devel@… added; erikb removed

Changed 7 years ago by jg

  • verified unset

The verification failed.

Bug #1475 has the current bug report.

Changed 7 years ago by erikb

  • cc mpg@… added

We are waiting for a better sugar solution to knowing which activity is "active". Using a focus listener to turn the camera on/off is unacceptable since showing the task frame causes a focus event (and shuts down the camera).

This thread has further information: http://mailman.laptop.org/pipermail/sugar/2007-April/002069.html

Changed 7 years ago by tomeu

Yesterday we added an 'active' property to sugar.activity.Activity. The shell will set it to True or False when the user switches between activites. You can listen to changes on the 'notify::active' signal.

Is this enough?

Changed 7 years ago by kimquirk

  • verified unset
  • milestone changed from BTest-4 to Trial-2

Moving to next software release, Trial-2.

Changed 7 years ago by jg

X can tell you when you are "visible", rather than having input focus. I would argue that etoys should use this as how to key on whether it should release the hardware than using focus.

I think it is unwise to have dependencies on Sugar when unnecessary, and I do not it think it necessary in this case.

Changed 7 years ago by erikb

bug filed to request fix the firing of notify::active events in 2026

Changed 7 years ago by jg

Heh...

This does not have to wait for Sugar.

As I pointed out in a camera bug on this issue, the ICCCM/EWMH documents define ways you can know you are visible or not.

So at least for many applications, they should be keying on visibility and not have to deal with any sugar information. This will help portability to non-sugar environments.

This won't always be true: but for activities where it does they should definitely use the standard X mechanisms and not any sugar mechanisms.

Chris, are there any offending applications at this time? If there are, there should be trac issues for each of them.

Changed 7 years ago by jg

  • component changed from distro to tinderbox

Changed 7 years ago by jg

  • milestone changed from Trial-2 to Trial-3

Changed 7 years ago by jg

  • milestone changed from Untriaged to V1.1

Changed 4 years ago by cjl

  • next_action set to never set

Is there any point in keeping tinderbox bugs open? Is this even a tinderbox bug?

Changed 4 years ago by cjb

  • status changed from new to closed
  • resolution set to wontfix

Closing.

Note: See TracTickets for help on using tickets.