Non-functioning Fn Special Key for Vol Mute + Errant Keyboard LED

Bug #713206 reported by inverser
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hello, first off thank you for taking the time to look at my bug. I hope you can help me to resolve it for the Voodoo Envy 133 owners out there that are interested in Ubuntu.

I am running Maverick Meerkat and 99% of Ubuntu runs flawlessly right out of the box. The problem I have is with the Fn+F11 key, which is the Voodoo Special Key for volume mute. F11 itself works fine. I use it with Guake daily. But pressing Fn+F11 locks me out of the keyboard. Keystrokes are no longer registered on the machine until I Cntrl+Alt+Backspace.

#
#
# xev output for mute key (Fn+F11) is as follows:

FocusOut event, serial 36, synthetic NO, window 0x5400001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 36, synthetic NO, window 0x5400001,
    mode NotifyWhileGrabbed, detail NotifyNonlinear

FocusOut event, serial 36, synthetic NO, window 0x4200001,
    mode NotifyGrab, detail NotifyAncestor

# xev output for F11 key is as follows:

KeyPress event, serial 36, synthetic NO, window 0x5400001,
    root 0xac, subw 0x0, time 6536115, (502,-375), root:(505,220),
    state 0x0, keycode 95 (keysym 0xffc8, F11), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x5400001,
    root 0xac, subw 0x0, time 6536229, (502,-375), root:(505,220),
    state 0x0, keycode 95 (keysym 0xffc8, F11), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

FocusOut event, serial 36, synthetic NO, window 0x5400001,
    mode NotifyNormal, detail NotifyNonlinear

#
#
#

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-25-generic 2.6.35-25.44
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: christopher 1608 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc400000 irq 45'
   Mixer name : 'Silicon Image SiI1392 HDMI'
   Components : 'HDA:10ec0268,103c2001,00100101 HDA:10951392,ffffffff,00100000'
   Controls : 16
   Simple ctrls : 8
Date: Fri Feb 4 11:25:45 2011
HibernationDevice: RESUME=UUID=6ddfc270-cb91-44cd-81bd-276ec2bfcd83
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Hewlett-Packard HP Gaming PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=48d0100e-430b-46e5-a76f-92c78c947ca6 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38.3
SourcePackage: linux
dmi.bios.date: 10/15/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.09
dmi.board.name: 2001
dmi.board.vendor: Flextronics
dmi.board.version: F008
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Flextronics
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.09:bd10/15/2008:svnHewlett-Packard:pnHPGamingPC:pvrF.08:rvnFlextronics:rn2001:rvrF008:cvnFlextronics:ct10:cvrN/A:
dmi.product.name: HP Gaming PC
dmi.product.version: F.08
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
inverser (resrevni) wrote :
Revision history for this message
inverser (resrevni) wrote :
Revision history for this message
inverser (resrevni) wrote :

Note: The mute LED is on an always-lit state and does not toggle when Fn+F11 is pressed. It would be great if this were resolved also.

Please let me know if you need any more information.

Thank you.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi inverser,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
inverser (resrevni) wrote :

Hello, Jeremy. I have installed linux-image-2.6.38-999-generic_2.6.38-999.201102221357_i386.deb from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

tags: added: apport-collected
description: updated
description: updated
tags: removed: needs-upstream-testing
Revision history for this message
inverser (resrevni) wrote :

I suppose I should say that bug is persistent in the new kernel. Hope to have this resolved. Thank you.

Changed in linux (Ubuntu):
status: Incomplete → New
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

inverser, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: needs-full-computer-model needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.