Ubuntu 10.10 Samsung R528 Function Keys don't work properly

Bug #674005 reported by Peter Roos
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned

Bug Description

On a Samsung R528 Laptop, I've installed Ubuntu 10.10
The problem also appeared in Ubuntu 10.04 Long Time Support.
Both systems are 64bit.

The FN + UP and DOWN buttons supposed to adjust screen brightness.
If i use this combination, it actually works. So the brightness bar appears in the right corner, and the bar
gets longer or shorter. But the brightness itself doesn't change. What is also interesting:
If i pull out AC, the brightness stays on the same level. What is more, if i turn on the laptop with
AC on, the brightness will be on MAX, and will stay on that level until new restart. And if I turn on
the laptop with AC off, it'll stay on 50% brightness. No matter if i plug in or out the AC during on state,
the brightness doesn't change. So that means, if the laptop is on low brightness, i have to turn off laptop.
Then plug in AC, and then turn on laptop again. By doing this, i'll have max brightness.
In addition, some of the FN + F* function keys don't work. The others work normally. One or two more doesn't work, but it's okay, because they supposed to run special sam
In my opinion, F3, F4, F5, F9 should work.
FN + F3 Euro button (same as alt gr +u)
FN + F4 Monitor Change button
FN + F5 Monitor Off button
FN + F9 Wifi ON/OFF button

Installed all updates, and checked for additional drivers (there isn't any).

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: evince 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Thu Nov 11 14:01:06 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
SourcePackage: evince

Revision history for this message
Peter Roos (roospeteristvan) wrote :
Revision history for this message
Book 'em Dano (heymrdjd) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. Please include the information requested at https://wiki.ubuntu.com/DebuggingKeyBoardDetection as separate attachments.

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Peter Roos (roospeteristvan) wrote :

I don't understand clearly, what I have to do with the given link. Please give me instructions how to proceed.

Revision history for this message
Book 'em Dano (heymrdjd) wrote :

I apologize, I gave you the incorrect url. Please include the information requested at https://wiki.ubuntu.com/DebuggingKeyboardDetection and https://wiki.ubuntu.com/Hotkeys/Troubleshooting as separate attachments.

Revision history for this message
Peter Roos (roospeteristvan) wrote :
Revision history for this message
Peter Roos (roospeteristvan) wrote :
Revision history for this message
Peter Roos (roospeteristvan) wrote :

Oh my god, I so don't have the time to make myself understand the knowledge of the second link.
Sorry, but I must learn for my exams.
But if You give me commands to copy and paste into terminal, I'll do it.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.