Samsung Laptop Hot Keys

Bug #601514 reported by Naraayan
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu 10.04 32 BIT

Device - Samsung R528 Laptop

Package Version - Unaware (Basic User)

The FN hotkeys in this laptop are not working. All the hotkeys except volume control are not working.

Upon using the FN Hotkeys - Nothing happens. Please advise as I dont wish to return to MS Win.

priya (priyamtk)
affects: ubuntu → gtkhotkey (Ubuntu)
Revision history for this message
Leo Arias (elopio) wrote :

Hello Naraayan,

Thanks for taking your time to report this issue and help us making ubuntu better.

Hotkey handling, such as volume and suspend keys, involves multiple packages. Please take a look at https://wiki.ubuntu.com/Bugs/FindRightPackage#Hotkeys
There is a section called "Step-by-step Troubleshooting". Please follow the steps and report back the results you get as comments. And in case of doubt, don't hesitate to ask here.

Please also add as separate attachments all the files requested in the section "Useful Information to Collect in Reports".

pura vida.

Changed in gtkhotkey (Ubuntu):
status: New → Incomplete
Revision history for this message
Leo Arias (elopio) wrote :
Revision history for this message
Leo Arias (elopio) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Naraayan (k-naraayan) wrote : Re: [Bug 601514] Re: Samsung Laptop Hot Keys

Well that's cause half the questions that are mandatory on the form are like greek to me!

Its actually a very small issue - the FN keys for brightness adjustment don't work - volume does work - but not brightness. If I start the machine without AC power it starts dim and I cannot adjust it manually. It does not become bright on its own when I switch on power in between.

The only way is to start the PC with AC power to get full brightness. So the Function keys for brightness would help. Kindly advise.

------Original Message------
From: Leo Arias
Sender: <email address hidden>
To: Naraayan Kannan
ReplyTo: Bug 601514
Subject: [Bug 601514] Re: Samsung Laptop Hot Keys
Sent: Aug 25, 2010 01:20

We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!

--
Samsung Laptop Hot Keys
https://bugs.launchpad.net/bugs/601514
You received this bug notification because you are a direct subscriber
of the bug.

Status in “gtkhotkey” package in Ubuntu: Incomplete

Bug description:
Ubuntu 10.04 32 BIT

Device - Samsung R528 Laptop

Package Version - Unaware (Basic User)

The FN hotkeys in this laptop are not working. All the hotkeys except volume control are not working.

Upon using the FN Hotkeys - Nothing happens. Please advise as I dont wish to return to MS Win.

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/gtkhotkey/+bug/601514/+subscribe

Regards,

Naraayan

The needs of the many outweigh the needs of the few; or the one ~
Vulcan Philosophy.

Sent from BlackBerry®

Revision history for this message
Leo Arias (elopio) wrote :

Hi Naraayan,

Thanks for your reply. Unfortunately we require more information to find the problem. And in order to collect that information you will have to run some commands on the terminal.

But we can help you translating the greek and we have a lot of patience :)

The instructions that you will find at https://wiki.ubuntu.com/Hotkeys/Troubleshooting are only a series of commands that you will have to type on the terminal.

First, go to Applications>Accesories>Terminal and enter the command:
killall gnome-settings-daemon gnome-power-manager

That will finish some applications that take the input from keyboard. So now you should be able to start the troubleshooting.

The next step is to enter on the terminal:
xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p'

A small window will be opened. Try to adjust the brightness with that window focused. If a keypress event is recognized, the code for that event will be printed in the terminal.

We need you to tell us if there was a keypress. And if so, what is printed to terminal. If there was no keypress, you should continue troubleshooting on step 4.

In case of doubt, just ask.

thanks,
pura vida.

Revision history for this message
Naraayan (k-naraayan) wrote :
Download full text (4.0 KiB)

This is what happened - I think I am getting the hang of what you experts
are testing. Though the key-press logged an event - nothing on screen in
terms of brightness changed.

So we now know that the function keys are working - but the function key is
not changing the brightness for some other reason - if my simpleton mind is
moving logically :)

Let me know what next - I feel like I am some in some Hollywood writing code
for some movie already :)

Thanks dude,

Naraayan

naraayan@HAL9000:~$ killall gnome-settings-daemon gnome-power-manager
naraayan@HAL9000:~$ xev | sed -n 's/^.*state \([0-9].*\), keycode
*\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p'
keycode 36 = (keysym 0xff0d, Return), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0
keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0
keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0
keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0
keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0
keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0
keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0
keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0

Regards,

Naraayan

The West won the world not by the superiority of its ideas or values or
religion, but rather by its superiority in applying organized violence.
Westerners often forget this fact, non-Westerners never do ~ Samuel P
Huntington.

On 25 August 2010 10:56, Leo Arias <email address hidden> wrote:

> Hi Naraayan,
>
> Thanks for your reply. Unfortunately we require more information to find
> the problem. And in order to collect that information you will have to
> run some commands on the terminal.
>
> But we can help you translating the greek and we have a lot of patience
> :)
>
> The instructions that you will find at
> https://wiki.ubuntu.com/Hotkeys/Troubleshooting are only a series of
> commands that you will have to type on the terminal.
>
> First, go to Applications>Accesories>Terminal and enter the command:
> killall gnome-settings-daemon gnome-power-manager
>
> That will finish some applications that take the input from keyboard. So
> now you should be able to start the troubleshooting.
>
> The next step is to enter on the terminal:
> xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\),
> .*$/keycode \2 = \3, state = \1/p'
>
> A small window will be opened. Try to adjust the brightness with that
> window focused. If a keypress event is recognized, the code for that
> event will be printed in the terminal.
>
> We ne...

Read more...

Leo Arias (elopio)
Changed in gtkhotkey (Ubuntu):
status: Incomplete → New
Revision history for this message
Leo Arias (elopio) wrote :

Please enter the following commands on the terminal, and add the resulting files as separate attachments:

udevadm info --export-db > udev-db.txt
dmesg > dmesg.log
sudo lsinput > lsinput.log
xkbcomp -xkb :0 - > xkbcomp.txt
setxkbmap -print > xkbmap.txt

affects: gtkhotkey (Ubuntu) → gnome-power-manager (Ubuntu)
Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Leo Arias (elopio) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Naraayan (k-naraayan) wrote :

Hey Leo,

I did what you asked last time and tried typing all that but nothing
happened.

The brightness increase and decrease doesnt work. Its cool. Ill try using
these codes again.

Regards,

Naraayan

"vi veri veniversum vivus vici" ~ "By the power of truth, I, while living,
have conquered the universe"

On 21 December 2010 06:06, Leo Arias <email address hidden> wrote:

> Please enter the following commands on the terminal, and add the
> resulting files as separate attachments:
>
> udevadm info --export-db > udev-db.txt
> dmesg > dmesg.log
> sudo lsinput > lsinput.log
> xkbcomp -xkb :0 - > xkbcomp.txt
> setxkbmap -print > xkbmap.txt
>
> ** Package changed: gtkhotkey (Ubuntu) => gnome-power-manager (Ubuntu)
>
> ** Changed in: gnome-power-manager (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/601514
>
> Title:
> Samsung Laptop Hot Keys
>
> Status in “gnome-power-manager” package in Ubuntu:
> Incomplete
>
> Bug description:
> Ubuntu 10.04 32 BIT
>
> Device - Samsung R528 Laptop
>
> Package Version - Unaware (Basic User)
>
> The FN hotkeys in this laptop are not working. All the hotkeys except
> volume control are not working.
>
> Upon using the FN Hotkeys - Nothing happens. Please advise as I dont wish
> to return to MS Win.
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/601514/+subscribe
>

Revision history for this message
Leo Arias (elopio) wrote :

Hi Naraayan,

The commands I send you should have created some files:
udev-db.txt
dmesg.log
lsinput.log
xkbcomp.txt
xkbmap.txt

You will find them on your home directory if you just opened the terminal and typed the commands.
Please attach them to this issue.

thanks.

Revision history for this message
Leo Arias (elopio) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-power-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Carsten Maass (cm-k) wrote :

I am experiencing the exact same problem under Lucid on a Samsung E452 notebook (Model: NP-E452-JS05DE).

The function keys which are not working are:

Fn+F5 (Backlight on/off), Scancode=0x84, Keycode=148=XF86Launch1
Fn+F7 (run Samsung Magic Doctor), Scancode=0xB1, Keycode=149=XF86Launch2
Fn+F8 (switch power mode), Scancode=0xB3, Keycode=202=Xf86Launch3
Fn+F9 (wlan), Scancode=0x86, Keycode=238=XF86WLAN
Fn+Up (brightnessup), Scancode=0x88, Keycode=225=XF86MonBrightnessUp
Fn+Down (brightnessdown), Scancode=0x89, Keycode=224=XF86MonBrightnessDown

Attached you will find the required debug information.

Greetings,
Carsten.

Revision history for this message
Carsten Maass (cm-k) wrote :
Revision history for this message
Carsten Maass (cm-k) wrote :
Revision history for this message
Carsten Maass (cm-k) wrote :
Revision history for this message
Carsten Maass (cm-k) wrote :
Revision history for this message
Carsten Maass (cm-k) wrote :
Revision history for this message
Carsten Maass (cm-k) wrote :
Revision history for this message
Carsten Maass (cm-k) wrote :
Revision history for this message
Carsten Maass (cm-k) wrote :

For this trace i pressed Fn+F5 twice, Fn+Up and Fn+Down once.

Changed in gnome-power-manager (Ubuntu):
status: Expired → New
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.