> right, we still need to change other components, I've tagged the verification-done because the only piece up for verification at the moment is libx11 and you verified that one, getting it in updates would put us one step closer from fixing the issue right?
This is exactly right. >> Additionally, this requires a revert of xkeyboard-config that we have in >> -proposed. I'm not sure how to work that because this is my first >> verification-failed bug, but I assume I can just revert it. > > Do you need revert or extra changes? in any case the update is in > precise-updates so you can't verification-failed it anymore (that's just used > to get things dropped from proposed/not copied to updates), you need another > upload on top of the current version This is in relation to bug #937822. Since that bug is verification- failed, we pulled the update of xkeyboard-config from the -proposed archive. But it's still living out in the launchpad bzr code archive. So specifically, my question is whether I should branch from the -updates lp archive or the -proposed lp archive (and pull the patch, as I have have done). I've ran into this situation before in bug 1011073 but cyphermox solved it for me. Sorry if this is too much minutia. https://code.launchpad.net/~ubuntu-branches/ubuntu/precise/xkeyboard-config/precise-updates https://code.launchpad.net/~ubuntu-branches/ubuntu/precise/xkeyboard-config/precise-proposed ** Also affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project raring series: Won't Fix Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “libx11” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Fix Released Status in “x11proto-core” package in Ubuntu: New Status in “xkeyboard-config” package in Ubuntu: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Won't Fix Status in “gnome-settings-daemon” source package in Precise: New Status in “libx11” source package in Precise: Fix Committed Status in “udev” source package in Precise: New Status in “x11proto-core” source package in Precise: Fix Released Status in “xkeyboard-config” source package in Precise: New Status in “xserver-xorg-input-evdev” source package in Precise: Won't Fix Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “libx11” source package in Raring: New Status in “udev” source package in Raring: Triaged Status in “x11proto-core” source package in Raring: New Status in “xkeyboard-config” source package in Raring: New Status in “xserver-xorg-input-evdev” source package in Raring: Won't Fix Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 00000080 0000101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x3400001, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x3400001, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
