Fn-key locks up computer

[s]

When using the keyboard shortcut on my Fujitsu-Siemens Amilo Li1818 laptop to alter the sound volume, it locks up.

If I press Fn-F5 to turn the volume up one notch (or F6 to turn it down), the computer will respond to this as if I was holding the keys and not releasing. After this All keys are dead, part from Fn-F5 or Fn-F6. Also it becomes impossible to open the menus in gnome. So The computer needs to be rebooted to work properly again.

Fn-F7 and Fn-F8 for screen lighting works flawlessly.

I am currently using Ubuntu 8.10 Intrepid Ibex, kernel 2.6.27-7-generic. It has been present since I first tried 8.10 out with the release candidate. This bug was not present in 8.04, though I have found it in Fedora 9 and 10beta.

[gaganian (nikosgrigo)]

I also coonfirm this bug in my Fujitsu-Siemens Amilo Pi2550. This bug was not present in 8.04.

[gaganian (nikosgrigo)]

The computer does not need to be rebooted it works even with log out and log in again

[Giuseppe Pantanetti (sep)]

This bug affects me too on a Fujitsu Amilo Pi1505. I managed to unfreeze the system by restarting bdus daemon.

 - I switched to terminal with Ctrl-Alt-F1
 - I logged in and executed: sudo /etc/init.d/dbus restart
 - Switched back to X server with Alt-F7 and all was ok

This procedure doesn't, luckly, involve logging out.

[Giuseppe Pantanetti (sep)]

Ok. I think it's a bluetooth problem: I unfreezed the system by stopping bluetooth services (my laptop doesn't have bluetooth...).
Maybe the acpi event fired by pressing Fn-F5/Fn-F6 involves bluetooth. I'm search for the script called by these buttons and seeing if there's a bluetooth invocation to disable.
More will follow.

[s (simon-wrafter)]

I tried Giuseppe Pantanetti's method (Ctrl-Alt-F1) and found that all I needed to do was to log back in directly, no dbus restart necessary.

[GarethMB (garethmbowen)]

I also suffer from this bug on a packard bell easynote e2316. My keybinding for volume control is however fn F3 or F4.

[Marton Balazs (balazs-math)]

Confirmed on AMILO Xi 2428. I did a showkey log after Ctrl-Alt-F1 and stopping hotkeys, and indeed: my fn-mute, fn-volume down and fn-volume up key releases are not noticed by the system:

keycode 28 release (initial release of return)
keycode 4 press (tested the stuff by pressing "4")
keycode 4 release (released "4")
keycode 113 press (pressed fn-mute (fn-F3), notice no release event)
keycode 5 press (tested by pressing "5")
keycode 5 release
keycode 114 press (pressed fn-volume down (fn-F4), again no release noticed)
keycode 6 press (test by pressing "6")
keycode 6 release
keycode 115 press (pressed fn-volume up (fn-F5))
keycode 7 press (test by "7")
keycode 7 release

These all worked perfectly in 8.04. fn-brightness down (fn-F8) and up (fn-F9) are still working flawlessly.

[lm2b (lm2b)]

Same problem in a CCE wm73c notebook, ubuntu 8.10.
Like Marton says, fn+mute, fn+volup, fn+voldown do'nt register the key release.
All others fn commands work.

[lm2b (lm2b)]

Same bug as https://bugs.launchpad.net/ubuntu/+bug/278781.
Patched at http://ubuntuforums.org/showthread.php?t=974723

[Richard W (richardwellons)]

I am also experiencing this problem with Dell Inspiron 6000. The scroll Lock is not functional, but doesn't cause a lock up. The brightness control launches the on screen notification but then locks the keyboard and the mouse seems to work only intermittently. Toggling to the terminal and back seems to restore functionality.

[s (simon-wrafter)]

as commented above this is a duplicate of an other bug. Thanks for the heads up!

[iomiappoggio (iomiappoggio)]

I also coonfirm this bug in my Fujitsu-Siemens Amilo Pi1505. This bug was not present in 8.04.

Does the patch at http://ubuntuforums.org/showthread.php?t=974723 work fine and easy?

[Attila Franczen (marrow)]

This bug is also present on my Amilo Pa1510 running Intrepid. And as mentioned above, this was not present in Hardy.

[jetdog (slicksterdave)]

Marked bug as non-duplicate.

If this volume-control/repeat-forever bug is still affecting you:

It has come to my attention that there is a flood of keyboard volume button/wheel =hardware= quirks that have never been dealt with, all having the same general problems: you press volume button (up or down), volume goes all the way up or down, and then your input becomes unresponsive.

To keep a long story short, there is a fair chance (though not guaranteed) that this is a kernel input driver bug/quirk for your volume control input device. (and even if not, the following will help determine what is wrong)

What I need the bug submitter to do (if not already), is to provide a model number for their laptop/desktop (or if custom-built, provide the model number of your: keyboard or multimedia device with the volume control realted to this bug)

- and if you could please, put that model number in the summery with something like this:
"Toshiba Satellite U300 volume button repeating forever"

If we can keep these volume control bugs pertaining to the __system/hardware in question__, it will help the maintainers a lot more.

Althought I can't guarantee/guess immediately what is going on here, what I will suggest is:

Provide some logs of the following:
(If you get some logs that run forever, please cut them short)

# echo "dmidecode > mydmilog.txt" | sudo bash

# echo "showkey -s > mykeylog.txt" | sudo bash
(use your volume up, volume down, volume up, and then volume down)

# echo "xev > myxevlog.txt" | sudo bash
(use your volume up, volume down, volume up, and then volume down)

This will greatly assist the maintainers in understanding and dealing with your bug.

Hopefully this helps speed these problems along :)

[Attila Franczen (marrow)]

Even though I am not the bug submitter, I have attached the two logs you asked for.

[Marton Balazs (balazs-math)]

As I wanted to check again I noticed that the problem disappeared on my Amilo Xi 2428. Since my earlier post I did an upgrade from Ubuntu 8.10 to 9.04, so now:
Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux,
maybe that solved the problem.

[Dr. Amr Osman (dr3mro)]

I confirm same issue since intrepid ibex but the patch was working ok
http://ubuntuforums.org/showthread.php?t=974723

yestreday i did upgrade to karmic but its again and the patch is not working in karmic
is there a new fix or a workaround sooon plz
???

[Scott Albertine (mechaphoenix25)]

This bug happens as well in Karmic, for volume up/down only, on the Dell Studio 1555, 1557, and 1558 models. See http://ubuntuforums.org/showthread.php?t=1401746 for a discussion with several confirming reports. A temporary fix I discovered is to turn off key-repeat entirely, which alleviates the problem somewhat. Is there any chance someone can come up with a xmodmap script of some sort to remap the volume keys to a "press and release" action, if such a thing exists? That should solve the issue completely

[MillenniumBug (millenniumbug)]

There is maybe a solution in
http://ubuntuforums.org/showthread.php?t=974723 , post 54

[Jerone Young (jerone)]

Can someone try 10.04? .. there is a fix for this is 10.04.

[Forest Monsen (forest.monsen)]

I have observed the volume up / volume down issue (<a href="http://ubuntuforums.org/showpost.php?p=6127623&postcount=1">apparently KEY_DOWN is reported, but not KEY_UP</a>) on Lucid/10.04, Dell Studio 1558 hardware.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi s,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 293642

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 293642 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/293642

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[jonie (jonie)]

I think the underlying cause of this bug is still present in Lucid.

Steps to recreate:

Activate SWCursor option in xorg. This will make the cursor refresh slower (and is needed in some workaround scenarios).
Open a text file in an X based text editor.
Start to move the cursor around by holding down the left/right arrow buttons.
After just a second the key input will start to repeat forever, locking any other X input.
Depending on key repeat speed set in Gnome preferences the problem may or may not occur.

There may be some kind of overflow in X that causes the key input to repeat forever.

[Fabio Marconi (fabiomarconi)]

Hello jonie.
We need exact information.
Still this issue reproducible with the latest updated Lucid packages ?
:)Fabio

[Fabio Marconi (fabiomarconi)]

Hello.
In order to confirm this bug and let developer start from here, we need more additional info.
can someone open a terminal and type this command :
apport-collect 293642
Thanks in advance.
:)Fabio

[jonie (jonie)]

Architecture: i386
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
MachineType: TOSHIBA Satellite M70
Package: xserver-xorg-input-evdev 1:2.3.2-5ubuntu1
PackageArchitecture: i386
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=75ffa061-25f6-44b8-ac61-07452816b281 ro hpet=disable acpi_osi=Linux nomodeset quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Tags: lucid lucid
Uname: Linux 2.6.32-24-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
dmi.bios.date: 12/12/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.70
dmi.board.name: HTW00
dmi.board.vendor: TOSHIBA
dmi.board.version: Null
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd12/12/2008:svnTOSHIBA:pnSatelliteM70:pvrPSM71E-02H01XS4:rvnTOSHIBA:rnHTW00:rvrNull:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite M70
dmi.product.version: PSM71E-02H01XS4
dmi.sys.vendor: TOSHIBA
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-24-generic

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[jonie (jonie)]

apport information

[Fabio Marconi (fabiomarconi)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Eskil (eskilbjerremikkelsen)]

This bug is present on my laptop (vega u50) running 10.04
Looking forward to a fix

[jonie (jonie)]

After this summer updates to xorg-core I can't reproduce this bug (key repeating infinitely to be specific) anymore on my Toshiba M70. Maverick seems not to be affected either, as far as my computer is concerned.

Perhaps, we should change affects xserver-xorg-input-evdev -> xserver-xorg-core?

[Dr. Amr Osman (dr3mro)]

afix will be available in a few minutes at
https://launchpad.net/~dr3mro/+archive/xserver-xorg-input-evdev

[Fabio Marconi (fabiomarconi)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

[Carsten (somehow-different)]

This bug still affects me. First encountered in Maverick. Still to be solved in Precise. I have a FSC Amilo Pi 1505. System freezes upon usage of Fn F5/F6? Do you need more information. I'd like to provide.

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-input-evdev (Ubuntu) because there has been no activity for 60 days.]