Volumecontrol FN+VolumeUP/VolumeDOWN lockup computer

Bug #1011323 reported by Klaas Eenkhoorn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
Undecided
Martin Pitt

Bug Description

After installing Ubuntu 12.04 64bit i have the same problem as in Ubuntu 11.10 64bit but this time it can not be fixed the way i did in 11.10.

I have a Fujitsu Amilo PI 1505 laptop with FN+VolumeUp en Down keys but when i use them the system locks up because the key's keep repeating.
For 11.10 i had a fix available for evdev_drv.so but the code in 12.04 is changed so i can not apply the fix described in: http://ubuntuforums.org/archive/index.php/t-974723.html
The fix was incorporating an extra filter which added a key_up event after the key_down.
But in the current source of evdev_drv.so (version 2.7.0) there is no such filter section.

WORKAROUND: Created file: /lib/udev/keymaps/force-release/fujitsu-amilo_pi-1505
containing:
0xAE #volume down
0xB0 #volume up

added udev rule for:
Vendor: FUJITSU SIEMENS
Product: AMILO Pi 1505

in file:
/lib/udev/rules.d/95-keyboard-force-release.rules

ENV{DMI_VENDOR}=="FUJITSU SIEMENS", ATTR{[dmi/id]product_name}=="AMILO Pi 1505", RUN+="keyboard-force-release.sh $devpath fujitsu-amilo_pi-1505"

I didn't test if common-volume-keys is sufficient, used for an allready existing udev rule. This file contains the same scan codes but written in lowercase. Confirmed by testing, adding my model 'AMILO Pi 1505' to the udev rule in the rule file '95-keyboard-force-release.rules':
ENV{DMI_VENDOR}=="FUJITSU SIEMENS", ATTR{[dmi/id]product_name}=="AMILO Si 1848+u|AMILO Xi 2428|AMILO Pi 1505", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

Fixes my the problem to and is the better option.

Package info: xserver-xorg-input-evdev-2.7.0
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: klaas 2685 F.... pulseaudio
 /dev/snd/pcmC0D6c: Slmodemd 995 F.... slmodemd
 /dev/snd/pcmC0D6p: Slmodemd 995 F.... slmodemd
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0000000 irq 45'
   Mixer name : 'Realtek ALC861'
   Components : 'HDA:10573055,10573055,00100700 HDA:10ec0861,15840000,00100300'
   Controls : 21
   Simple ctrls : 14
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=331b48c1-a023-49f4-b359-e10931b1be91
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: FUJITSU SIEMENS AMILO Pi 1505
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic root=UUID=8b84843e-ba72-43f5-8561-7a0d71570c9d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/klaas not ours.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic N/A
 linux-backports-modules-3.2.0-24-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: precise precise
Uname: Linux 3.2.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/15/2007
dmi.bios.vendor: FUJITSU SIEMENS
dmi.bios.version: 1.13C
dmi.board.name: AMILO Pi 1505
dmi.board.vendor: FUJITSU SIEMENS
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: dmi:bvnFUJITSUSIEMENS:bvr1.13C:bd03/15/2007:svnFUJITSUSIEMENS:pnAMILOPi1505:pvr:rvnFUJITSUSIEMENS:rnAMILOPi1505:rvr:cvnFUJITSUSIEMENS:ct10:cvr:
dmi.product.name: AMILO Pi 1505
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1011323/+editstatus and add the package name in the text box next to the word Package.

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

tags: added: bot-comment
Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote :

Package name:

root@laptop:~# dpkg -S evdev_drv.so
xserver-xorg-input-evdev: /usr/lib/xorg/modules/input/evdev_drv.so

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
tags: added: oneiric precise
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Can you please follow this steps:
https://wiki.ubuntu.com/Hotkeys/Troubleshooting
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1011323

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : AcpiTables.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : AlsaDevices.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : AplayDevices.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : ArecordDevices.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : BootDmesg.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : CRDA.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : IwConfig.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : Lspci.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : Lsusb.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : PciMultimedia.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : ProcEnviron.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : ProcModules.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : UdevDb.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : UdevLog.txt

apport information

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote :

Tracked the following key's:

/lib/udev/keymap -i input/event4

0xAE volumedown
0xB0 volumeup

These keys's are not released, allthough mentioned (in small caps) in the file /lib/udev/keymaps/force-release/common-volume-keys (???) this failes to work.
How should i create the file ' 95-keyboard-force-release.rules' with what layout ?

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote :

Solved my problem:

Created file: /lib/udev/keymaps/force-release/fujitsu-amilo_pi-1505
containing:

0xAE #volume down
0xB0 #volume up

added udev rule for:
Vendor: FUJITSU SIEMENS
Product: AMILO Pi 1505

in file: /lib/udev/rules.d/95-keyboard-force-release.rules

ENV{DMI_VENDOR}=="FUJITSU SIEMENS", ATTR{[dmi/id]product_name}=="AMILO Pi 1505", RUN+="keyboard-force-release.sh $devpath fujitsu-amilo_pi-1505"

I didn't test if common-volume-keys is sufficient, used for an allready existing udev rule.
This file contains the same scan codes but written in lowercase.

Does that make a difference ?

Revision history for this message
Klaas Eenkhoorn (k-eenkhoorn) wrote :

Confirmed by testing, adding my model 'AMILO Pi 1505' to the udev rule in the rule file '95-keyboard-force-release.rules' :

ENV{DMI_VENDOR}=="FUJITSU SIEMENS", ATTR{[dmi/id]product_name}=="AMILO Si 1848+u|AMILO Xi 2428|AMILO Pi 1505", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

Fixes my the problem to and is the better option.

Thanks for the support!

penalvch (penalvch)
tags: added: needs-upstream-testing
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

Applied the quirk for all AMILO models now: http://cgit.freedesktop.org/systemd/systemd/commit/?id=d4c44191b7

no longer affects: linux (Ubuntu)
Changed in udev (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
status: New → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package udev - 175-0ubuntu11

---------------
udev (175-0ubuntu11) quantal; urgency=low

  * 00git-keymaps.patch: Update to latest keymaps from upstream systemd git
    head. Amongst them:
    - FUJITSU SIEMENS AMILO Pi 1505. (LP: #1011323)
    - Acer Aspire 5720 (LP: #1009836)
    - Mitac Mio N890 (LP: #998621)
    - Sony VPCEL2S1E (LP: #939868)
 -- Martin Pitt <email address hidden> Thu, 20 Sep 2012 10:43:55 +0200

Changed in udev (Ubuntu):
status: Fix Committed → Fix Released
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.