[Samsung NP350V5C-S07DE] Keyboard blocked after having used volume keys

[Torsten Bronger]

After having pressed Fn + Louder on my Samsung NP350V5C-S07, the volume is increased to max, and the keyboard is completely unresponsive from thereon. The system works normal, only the keyboard is blocked. I have to restart the machine.

Support page?:
http://www.samsung.com/uk/support/model/NP350V5C-S07DE-downloads

---
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bronger 1392 F.... lxpanel
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=68fbe940-90cd-457f-b3dd-ada0921a5891
InstallationDate: Installed on 2012-12-27 (0 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
MarkForUpload: True
Package: linux (not installed)
ProcFB:
 0 radeondrmfb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=8b7bdae8-1a26-4fcb-97ad-602fabd4e95d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-21-generic N/A
 linux-backports-modules-3.5.0-21-generic N/A
 linux-firmware 1.95
StagingDrivers: rts5139
Tags: quantal staging
Uname: Linux 3.5.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 06/30/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P04AAL
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP350V5C-S07DE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: BOARD REVISION 00
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04AAL:bd06/30/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04AAL.022.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S07DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
dmi.product.version: P04AAL.022.CP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1094066/+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.]

[Edward Donovan (edward.donovan)]

Perhaps a kernel issue; that's my first guess, anyway, at a package assignment. Thanks.

[Brad Figg (brad-figg)]

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

apport-collect 1094066

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.

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Torsten Bronger (bronger)]

apport information

[Brad Figg (brad-figg)]

This change was made by a bot.

[Vadim Evard (v-e-evard-w)]

Confirm on 13.04 and NP350E5C-S0A:
Result of pressing volume keys is unpredicatble and usually blocks keyboard. Not completely: Ctrl-Alt-F1 switches to tty, and after switching back keyboard works again; Ctrl-Alt-T launches terminal, and other shortcuts may work as well.

After going to tty and back volume keys produce no visible effect.
Showkey(1): pressed fn-f[678] aka mute, volume down, volume up
keycode 113 press
keycode 114 press
keycode 115 press

[penalvch (penalvch)]

Torsten Bronger, could you please provide the full computer model as noted on the sticker?

[Torsten Bronger (bronger)]

The model name on the sticker is NP350V5C-907DE.

[penalvch (penalvch)]

Torsten Bronger, I tried to to find the Samsung Deutchland Support page regarding this laptop, but so far I'm not finding it. Would you happen to have the URL for it?

[Torsten Bronger (bronger)]

http://www.samsung.com/de/consumer/notebooks-displays/notebook-computers/serie-3/NP350V5C-S07DE-gallery

[penalvch (penalvch)]

Torsten Bronger, because Samsung does not easily reveal what the latest BIOS is for this model, could you please download the latest firmware software as per http://www.samsung.com/de/support/model/NP350V5C-S07DE, and advise if a BIOS update is available? If so, when you update to this, does it change anything? If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[Torsten Bronger (bronger)]

I'm sorry but I can't do that I'm afraid. The level of suffering is not high enough for me to perform this procedure. Besides, it seems to work only with Windows installed, which is not the case in my case. Or does it also work from inside a VirtualBox?

[Launchpad Janitor (janitor)]

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

[Torsten Bronger (bronger)]

FWIW, a workaround is to switch to a console with Alt+Ctrl+F1 and switch back with Alt-Ctrl-F7. At least the infinite loop is then interrupted.

[Vadim Evard (v-e-evard-w)]

The bug is still here, with Xubuntu 14.04.1 on NP350E5C-S0A .
There seem to be a workaround for different models of notebooks: https://answers.launchpad.net/ubuntu/+source/udev/+question/237756, answer #7.

[penalvch (penalvch)]

Felagund, thank you for your comment. Unfortunately, this bug report is not scoped to you, your hardware, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs