Ubuntu
linux package

046d:c52b Logitech Wave keyboard multi-media keys don't all work

Bug #934480 reported by Jason Smith on 2012-02-17

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Incomplete	Medium	Seth Forshee

Bug Description

This image for reference: http://www.gratiscomputech.com/images/full_image/4864.jpg

Key status is as follows, from left to right:

3D Swither key (bottom left): Doesn't work
Zoom keys: Doesn't work
Config key: Doesn't work
Camera key: Works with hacked udev (to make the rules load the keymap)
Media control keys: All working
Music Key: Works but reports as Tools instead of Music (fixed with keymap fix)
Media Center Key: Reports same keycode as music key
Calculator: Works
Sleep: Works

Function Keys (pressing Fn+F#)
F1 - F3: Works
F4 - F6: Doesn't work
F7 - F10: Works
F11: Doesn't work
F12: Works
Print Screen/Pause Break: Works

evtest results:
I have also tested what keys produce output on *some* output device on evtest. I tried every output device to be sure.

3D Swither key (bottom left): No
Zoom keys: Yes
Config key: No
Camera key: Yes
Media control keys: Yes
Music Key: Yes
Media Center: Yes (same as Music Key)
Calculator: Yes
Sleep: Yes

Function Keys (pressing Fn+F#)
F1 - F3: Yes
F4 - F6: No
F7 - F10: Yes
F11: No
F12: Yes
Print Screen/Pause Break: Yes

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-16-generic 3.2.0-16.25
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: jason 29811 F.... pulseaudio
/dev/snd/controlC2: jason 29811 F.... pulseaudio
/dev/snd/controlC0: jason 29811 F.... pulseaudio
/dev/snd/pcmC0D0p: jason 29811 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf6500000 irq 53'
   Mixer name : 'Realtek ALC892'
   Components : 'HDA:10ec0892,15585102,00100302'
   Controls : 37
   Simple ctrls : 20
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xf6080000 irq 17'
   Mixer name : 'Nvidia GPU 15 HDMI/DP'
   Components : 'HDA:10de0015,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
Card2.Amixer.info:
Card hw:2 'U0x46d0x8d7'/'USB Device 0x46d:0x8d7 at usb-0000:02:00.0-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:08d7'
   Controls : 3
   Simple ctrls : 2
Date: Fri Feb 17 15:21:06 2012
HibernationDevice: RESUME=UUID=ab8087de-f629-47d2-ba08-f8471e7e6c1c
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: System76, Inc. Gazelle Professional
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-16-generic root=UUID=f5d007fc-0743-41b5-aa63-c0347cf9781d ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-16-generic N/A
linux-backports-modules-3.2.0-16-generic N/A
linux-firmware 1.69
RfKill:
0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-01-16 (32 days ago)
dmi.bios.date: 08/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: Not Applicable
dmi.board.name: Gazelle Professional
dmi.board.vendor: System76, Inc.
dmi.board.version: gazp6
dmi.chassis.asset.tag: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: gazp6
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp6:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp6:cvnSystem76,Inc.:ct10:cvrgazp6:
dmi.product.name: Gazelle Professional
dmi.product.version: gazp6
dmi.sys.vendor: System76, Inc.

Tags:

Revision history for this message

Jason Smith (jassmith) wrote on 2012-02-17:

AcpiTables.txt Edit (200.5 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (1.1 KiB, text/plain; charset="utf-8")
AplayDevices.txt Edit (685 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (399 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (60.6 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (3.8 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (15.2 KiB, text/plain; charset="utf-8")
Card1.Amixer.values.txt Edit (499 bytes, text/plain; charset="utf-8")
Card1.Codecs.codec.0.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.1.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.2.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.3.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card2.Amixer.values.txt Edit (320 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (38.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (519 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (14.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (620 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.1 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (4.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.0 KiB, text/plain; charset="utf-8")
PulseSinks.txt Edit (4.1 KiB, text/plain; charset="utf-8")
PulseSources.txt Edit (6.8 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (152.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (327.0 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (1.1 KiB, text/plain; charset="utf-8")

Changed in linux (Ubuntu):
assignee:	nobody → Seth Forshee (sforshee)

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2012-02-17:

Would it be possible for you to test the latest upstream kernel? It would be good to know if this bug is already fixed upstream. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory).

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc3-precise/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
tags:	added: needs-upstream-testing
Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Seth Forshee (sforshee) wrote on 2012-02-17:

There's some debugfs entries for hid devices that may be useful. I'm not sure yet what all the output means but it would be interesting at least to see whether anything appears for the buttons that aren't working. Note that working in debugfs requires doing everything as root.

You'll have a set of directories under /sys/kernel/debug/hid, one for each hid device. The ones that correspond to the keyboard (and mouse) will be of the format xxxx:046D:C52B:xxxx. Within each directory are two files, rdesc and events. For each of the events files corresponding to your keyboard/mouse, run 'cat events' and press the buttons to see if you get corresponding output. You'll have to hit Ctrl-C to cancel when you are done.

Let me know whether you see any data corresponding to the keys, and if so what output you get.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Jason Smith (jassmith) wrote on 2012-02-20:

There are 5 entries in there that matched the pattern you provided (they were also the only entries). All 5 of them failed to produce any kind of result when pressing the non-working buttons.

Revision history for this message

Seth Forshee (sforshee) wrote on 2012-02-23:

Okay, if you're not seeing output from any of the debugfs files then it seems to indicate that there's nothing coming over USB when these buttons are pressed. So I suspect there's some missing support from the driver. The driver was actually supplied by Logitech though, and I think the best hope of success is reporting the problem to the driver author and seeing if Logitech will provide a fix.

The easiest way to do this is probably a direct line of communication between you and the developer, and if that's something you'd be comfortable with I can give you contact information. Otherwise I can report the bug upstream.

Revision history for this message

Jason Smith (jassmith) wrote on 2012-02-28:

Im happy to work directly with logitech

Revision history for this message

Seth Forshee (sforshee) wrote on 2012-02-28:

Cool. I'd suggest reporting the bug to the author via email. His contact information is:

Nestor Lopez Casado <nlopezcasad at logitech dot com>

You should also Cc <email address hidden>, and feel free to Cc me too if you wish. I'll monitor the discussion on linux-input either way.

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2013-12-14:

Jason Smith, 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 just make a comment to this.

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc3

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.

summary:	- Logitech Wave keyboard multi-media keys don't all work + 046d:c52b Logitech Wave keyboard multi-media keys don't all work
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntulinux package

046d:c52b Logitech Wave keyboard multi-media keys don't all work

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package