[Dx-packages] [Bug 1397587] [NEW] Volume display does not update when changing default sink

2014-11-29 Thread Ben Harris
Public bug reported:

On my laptop I often have two PulseAudio sinks, the on-board audio
(alsa_output.pci-_00_1b.0.analog-stereo) and a Bluetooth speaker
(bluez_sink.8C_DE_52_2F_AF_F3).  I can choose the default destination
for sound output using the Sound pane of System Settings, and I can
separately change the volume setting of each sink using the paman
application.  When I adjust the volume using the sound menu, it affects
the default sink.  However, when I change to a different default sink,
the sound menu does not update and continues displaying the volume for
the previously-selected sink.  Only if I change the volume setting for
one of the sinks (e.g. using paman) does the sound menu update to show
the new volume level.

To reproduce:

Find a system with more than one sound sink.

Launch paman and open the Properties window for each sink.

Also open the Sound pane of System Settings.

Set one sink to maximum volume and one to minumum.

Switch between outputs using Systems Settings, and note that the sound
menu does not update to match the different volume settings of the two
sinks.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
Uname: Linux 3.16.0-25-generic i686
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
CurrentDesktop: Unity
Date: Sat Nov 29 19:10:52 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-motts-20100121-3
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-06-09 (1634 days ago)
InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 
20100121-21:52
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to trusty on 2014-08-15 (105 days ago)

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


** Tags: apport-bug i386 trusty

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

Title:
  Volume display does not update when changing default sink

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  On my laptop I often have two PulseAudio sinks, the on-board audio
  (alsa_output.pci-_00_1b.0.analog-stereo) and a Bluetooth speaker
  (bluez_sink.8C_DE_52_2F_AF_F3).  I can choose the default destination
  for sound output using the Sound pane of System Settings, and I can
  separately change the volume setting of each sink using the paman
  application.  When I adjust the volume using the sound menu, it
  affects the default sink.  However, when I change to a different
  default sink, the sound menu does not update and continues displaying
  the volume for the previously-selected sink.  Only if I change the
  volume setting for one of the sinks (e.g. using paman) does the sound
  menu update to show the new volume level.

  To reproduce:

  Find a system with more than one sound sink.

  Launch paman and open the Properties window for each sink.

  Also open the Sound pane of System Settings.

  Set one sink to maximum volume and one to minumum.

  Switch between outputs using Systems Settings, and note that the sound
  menu does not update to match the different volume settings of the two
  sinks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Nov 29 19:10:52 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-09 (1634 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 
20100121-21:52
  SourcePackage: indicator-sound
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (105 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1397587/+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 1326788] Re: debian/rules clean does not clean adequately

2014-06-05 Thread Ben Harris
I failed to mention: this problem affects Ubuntu 14.04 LTS.

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

Title:
  debian/rules clean does not clean adequately

Status in “unity-lens-applications” package in Ubuntu:
  New

Bug description:
  This is a problem in the unity-lens-applications source package.

  According to Ubuntu policy, the clean rule in debian/rules  must
  undo any effects that the build and binary targets may have had,
  except that it should leave alone any output files created in the
  parent directory by a run of a binary target.  That target in unity-
  lens-applications does not do this:

  root@chickatrice:/tmp# apt-get source 
unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 /dev/null 21
  root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc 
-l92
  root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011  
debian/rules build  debian/rules clean ) /dev/null 21
  root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc 
-l103
  root@chickatrice:/tmp# rm -r unity*
  root@chickatrice:/tmp# apt-get source 
unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 /dev/null 21
  root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011  
files.before
  root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011  
debian/rules build  debian/rules clean ) /dev/null 21
  root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011  
files.after
  root@chickatrice:/tmp# diff files.before files.after | grep '^'
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/aptd-client.c
   
unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-data-cache.c
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/xapian-utils.c
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/schemas.c
   
unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-utils.c
   
unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-app-details.c
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/utils.c
   
unity-lens-applications-7.1.0+13.10.20131011/tests/unit/purchase-info-helper.c
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/app-watcher.c
   unity-lens-applications-7.1.0+13.10.20131011/data/applications.scope
   unity-lens-applications-7.1.0+13.10.20131011/data/scopes.scope

  It looks like some of the files generating while building are not
  correctly removed while cleaning.  This is a problem if (as I do) you
  want to convert the package to use the 3.0 (quilt) source format.

  The attached patch fixes the problem, but probably more crudely than
  is acceptable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1326788/+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