Re: Default option for volume hotkeys (speakers/headphones)
On Sun, Aug 26, 2007 at 03:33:06PM +1200, Aaron Whitehouse wrote: 3) Cleverly determine whether headphones are plugged in. If they are, make the hotkeys control Headphones and if they are not, control Master. 4) Alter the kernel so that it binds the headphone and master channel together. That's how it's handled on various pieces of hardware. -- Matthew Garrett | [EMAIL PROTECTED] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Default option for volume hotkeys (speakers/headphones)
On 27/08/07, Matthew Garrett [EMAIL PROTECTED] wrote: On Sun, Aug 26, 2007 at 03:33:06PM +1200, Aaron Whitehouse wrote: 3) Cleverly determine whether headphones are plugged in. If they are, make the hotkeys control Headphones and if they are not, control Master. 4) Alter the kernel so that it binds the headphone and master channel together. That's how it's handled on various pieces of hardware. I have both Headphone and Master set to 50% and then bind the hotkey to PCM which affects them both as a workaround, but that wouldn't work on all systems. Would it be possible to create a virtual channel that affects both Master and Headphone channels, to which the hotkey can be bound? Arwyn -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Fwd: Join the Debian Python Applications Packaging Team
Forwarded FYI for those who have Python applications they'd like to try and get into Debian. I've worked with the people from Debian Python Modules Team that are setting this team up and they are very open to contribution from Ubuntu. Scott K -- Forwarded Message -- Subject: Join the Python Applications Packaging Team Date: Sunday 26 August 2007 14:54 From: Piotr Ożarowski [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hi, Do you need help with your Python application package but DPMT guys don't want to inject it in their repo because it's not a module? Do you have problems with finding sponsor due to this new nasty Debian Python Policy? I have something for you: new, shiny: *Python Applications Packaging Team* Interested? Read [1] or join us on #debian-python channel (OFTC network) [1] http://python-apps.alioth.debian.org/policy.html -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
