#9913 NORM 12.1.0: sugar frame speaker icon does not reflect volume hot key usage

Zarro Boogs per Child bugtracker at laptop.org
Wed Apr 18 17:56:30 EDT 2012


#9913: sugar frame speaker icon does not reflect volume hot key usage
--------------------------------+-------------------------------------------
           Reporter:  Andy Pei  |       Owner:  sayamindu                         
               Type:  defect    |      Status:  assigned                          
           Priority:  normal    |   Milestone:  12.1.0                            
          Component:  sugar     |     Version:  1.5 Software Build os64 aka 10.1.0
         Resolution:            |    Keywords:                                    
        Next_action:  design    |    Verified:  0                                 
Deployment_affected:            |   Blockedby:                                    
           Blocking:  10229     |  
--------------------------------+-------------------------------------------

Comment(by Quozl):

 the resources are only consumed when the speaker palette is displayed.
 this is rare.  therefore this should not be a concern.  however, as this
 doesn't yet work and would require invasive changes to the acme-volume-
 alsa program in the sugar-toolkit, it remains less practical than the use
 of snd_mixer_poll_descriptors.

 your solution of using gconf is effectively interprocess communication
 between olpc-volume and sugar.  it would require disk access for every
 change, shortening the life of the microSD or eMMC.  you would still need
 to re-read the gconf setting in a timed polling in order to display the up
 to date value.

 the use of snd_mixer_poll_descriptors will work with activities when they
 change volume.  measure and turtleart contain volume control manipulation
 code.

 pulseaudio uses alsa underneath, so i don't see how you can use that as an
 excuse to avoid the problem.  but it does bring up complexity.  olpc-
 volume uses alsa.  does the sugar team's intention to move to pulseaudio
 include changes for olpc-volume?  where's the design plan?

-- 
Ticket URL: <http://dev.laptop.org/ticket/9913#comment:29>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system


More information about the Bugs mailing list