This release has reached end-of-life [0].
[0] https://wiki.ubuntu.com/Releases
** Changed in: linux (Ubuntu Hardy)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nice to see you still care about this issue after all these years. I am
actually still using a device.
Am 18.08.2013 19:46 schrieb Julian Wiedmann 295...@bugs.launchpad.net:
This release has reached end-of-life [0].
[0] https://wiki.ubuntu.com/Releases
** Changed in: linux (Ubuntu Hardy)
I have reported recurrence of brightness control failure on nc10 running
Ubuntu 11.10 (kernel 3.0) as issue #883431.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295251
Title:
Samsung NC10
@Reuben, could you please open a new bug for this? You can reference
this one in the description but it helps to have a seperate instance to
track any steps on this re-occuring problem. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This worked fine for me for a long time, but seems to have stopped
working in oneiric: the brightness control works OK, but it goes all the
way up or down for each press of Fn+Up or Fn+Down (actually, it's a
little odder than that: Fn+Down always makes it go to minimum, then
Fn+Up once makes it go
I'm using an NC-10, BTW. All the quirks fixes mentioned above seem
still to be in place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295251
Title:
Samsung NC10 brightness keys block keyboard and
If I use the current natty 2.6.38-11 kernel, the brightness control
works fine again, so it seems to be a kernel problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295251
Title:
Samsung NC10
Martin, I just installed 10.10 Netbook Edition on my N145 and there
still appear to be problems here. I had to put *N* in the
/lib/udev/rules.d/95-keyboard-force-release.rules list to get the
keyboard to release but the brightness function keys have no effect
other than to temporarily.display
** Changed in: linux
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295251
Title:
Samsung NC10 brightness keys block keyboard and produce all-or-nothing
effect
--
This also affects the N145 on out-of-the-box Ubuntu 10.10.
I had to use the following steps to get Ubuntu working well on my N145:
http://twistedpairdevelopment.wordpress.com/2010/11/16/installing-ubuntu-on-a-samsung-n145-and-possibly-others/
The keyboard locking can simply be solved by adding
Adam, this was fixed for good in latest udev by applying the rule to all
Samsung computers.
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu Hardy)
Assignee: Andy Whitcroft (apw) = (unassigned)
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm using a new Samsung NB30 with Lucid and for me the Brightness
Up/Down buttons (FN up/down) neither work, nor does the toggle Backlight
button (Fn F5). The patch must have left the new kernel. I tried Fedora
13 Live CD and it has the same problem.
--
Samsung NC10 brightness keys block
Wysłane z iPhone'a
Dnia 2010-04-02 o godz. 04:37 frederik.nnaji
frederik.nn...@gmail.com napisał(a):
i'm using lucid on an NC10 and brightness still doesn't work.
how's that?
Which bios version fo you have?
Regards
Zygmunt
--
Samsung NC10 brightness keys block keyboard and produce
i'm using lucid on an NC10 and brightness still doesn't work.
how's that?
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Branch linked: lp:ubuntu/hardy-proposed/hal-info
** Branch linked: lp:ubuntu/intrepid-proposed/hal-info
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of
** Changed in: linux
Status: Confirmed = Fix Released
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package linux - 2.6.27-14.33
---
linux (2.6.27-14.33) intrepid-proposed; urgency=low
[Stefan Bader]
* Fix FTBS due to a mysteriously missing ABI directory.
linux (2.6.27-14.32) intrepid-proposed; urgency=low
[Stefan Bader]
* Rebuild of
Nonsense i was confused in my last post - lol.
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I come from 'Bug 219116 Multiple hotkeys don't work with Samsung R70
T7300 Despina' because it has the status of being duplicate of this one.
And I'm using Ubuntu 9.04 where some fn-keys are not working. And when I
compare 9.04 to 8.10 I lost the fn+f9 (wlan on/off) what was in 8.10.
Now working:
Sorry I mean that i come from Bug 295251.
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: linux (Ubuntu Intrepid)
Assignee: (unassigned) = Stefan Bader (stefan-bader-canonical)
** Changed in: linux (Ubuntu Hardy)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu Hardy)
Status: New = In Progress
--
Samsung NC10 brightness keys block keyboard
** Changed in: linux (Ubuntu Hardy)
Assignee: (unassigned) = Andy Whitcroft (apw)
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have had a look at the possibility of a Hardy backport for this. It
is not as simple a patch and therefore far from guarenteed to be
accepted as an SRU. But if there is anyone still on Hardy affected by
this and they could test this combination, then please could you test
the kernels at the
To sync status. The fix Input: atkbd - Samsung NC10 key repeat fix has
been integrated with stable update 2.6.27.15 and is included in the
2.6.27-13.29 kernel (currently in -proposed)
** Changed in: linux (Ubuntu Intrepid)
Importance: Undecided = Medium
Status: New = Fix Released
--
** Changed in: linux (Ubuntu Intrepid)
Status: Fix Released = Fix Committed
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is
SteveB, you have a different model. Please open a new bug report against
hal-info and submit output of lshal.
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of
I have a Samsung Q210 laptop running Intrepid.
The volume keys work perfectly (including on-screen graphic), but the
brightness keys have no effect at all. xev shows no events when these
keys are pressed. I have updated hal-info but there has been no effect.
Anything else I should try? Thanks.
I am very much confused here. How is this fixed with the hal-info
update. I have that package installed, and my function keys still will
not release... Am I missing something here?
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
This bug was fixed in the package hal-info - 20090128-0ubuntu1~intrepid2
---
hal-info (20090128-0ubuntu1~intrepid2) intrepid-proposed; urgency=low
* Add 01_disable_samsung_nc10_keymap.patch: Disable keymap for
Samsung NC10, since it causes X freezes on the intrepid kernel.
This bug was fixed in the package hal-info - 20090128-0ubuntu1~hardy2
---
hal-info (20090128-0ubuntu1~hardy2) hardy-proposed; urgency=low
* Add 01_disable_samsung_nc10_keymap.patch: Disable keymap for
Samsung NC10, since it causes X freezes on the intrepid kernel.
(LP:
Hello everyone,
would it be possible for someone to post a write-up of the fix (step-by-step
instruction) for those like me who are not so experienced with linux.
What should be the steps fix the fn keys problem on NC10. Is it just upgrading
to the '-proposed' or is there a need to modify the
I was poking around with the Samsung Q45 and discovered a work-around by
chance:
* press (amd release) the blue 'Fn' key *alone*
* depending on the focus that will open a menu somewhere on the desktop but
do not worry and just ignore that for a moment
* now use the Fn-Up/Down key
I have a Samsung Q45 laptop running Jaunty and exhibiting very much the
same problems when using the brightness control keys.
** Attachment added: dmesg output
http://launchpadlibrarian.net/22582860/dmesg.out
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
More info re. the Samsung Q45: the keys for brightness control are
recognised but there is no release:
This is the output from xev | sed -n 's/^.*state \([0-9].*\), keycode
*\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' :
keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state =
I am running the following kernel BTW:
Linux fn80 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009
x86_64 GNU/Linux
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you
Closing linux/jaunty task then, thanks for testing!
Could anyone also please test the current hal-info in intrepid/hardy-
proposed and confirm that it does *not* enable hotkeys on the NC10 any
more?
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
Samsung NC10
Zygmunt Krynicki [2009-02-09 19:08 -]:
It's still broken on .19 BTW (backlight control keys just hang the keyboard
in X)
That's an effect of a keypress acting as a series of indefinite
keypresses. Try switching to Ctrl+Alt+F1 and back, that helped on my
friend's NC10.
--
Samsung NC10
The current hardy/intrepid-proposed hal-info enable keymaps on the NC10.
I'm going to disable that again in a followup upload, so that people
don't get bitten by that bug.
** Changed in: hal-info (Ubuntu Intrepid)
Assignee: (unassigned) = Martin Pitt (pitti)
Status: New = Triaged
--
New hal-info uploaded to hardy/intrepid-proposed uploaded which fixes
this; waiting for Steve to process.
** Changed in: hal-info (Ubuntu Intrepid)
Status: Triaged = In Progress
** Changed in: hal-info (Ubuntu Hardy)
Status: New = In Progress
--
Samsung NC10 brightness keys block
** Changed in: hal-info (Ubuntu Hardy)
Status: In Progress = Fix Committed
** Changed in: hal-info (Ubuntu Intrepid)
Status: In Progress = Fix Committed
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You
Accepted hal-info into hardy-proposed and intrepid-proposed; please test
and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Samsung NC10 brightness keys
** Tags added: hw-specific
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have just tested this on NC10 (with 2.6.28.7-20) and it seems to work.
I have just one comment: compared to the speed of adjusting sound
(FN+left,right arrows) adjusting brightness (FN+up,down arrows) is about x2-x3
times slower.
--
Samsung NC10 brightness keys block keyboard and produce
Current hal-info in Jaunty sets the keymap for the NC10. The current
{hardy,intrepid}-proposed packages do that as well, but I'll pull them
(also) because of this kernel bug, which renders the hotkeys unusable.
** Changed in: hal-info (Ubuntu)
Status: In Progress = Fix Released
--
linux 2.6.28-7.20 (just uploaded to Jaunty) should fix this:
linux (2.6.28-7.20) jaunty; urgency=low
[ Tim Gardner ]
* SAUCE: Input: atkbd - Samsung NC10 key repeat fix
[...]
Could people please try this once it is built and hits the archive?
--
Samsung NC10 brightness keys block
I'll test that as soon as 2.6.28-7.20 hits the archive.
It's still broken on .19 BTW (backlight control keys just hang the keyboard in
X)
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification
I'll test that as soon as 2.6.28-7.20 hits the archive.
It's still broken on .19 BTW (backlight control keys just hang the keyboard in
X)
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification
@Chris and Cyril: I'm a bit confused, I'm not a linux expert and I thought I
did it right but obviously not. Now I tried again showkey -k and showkey -s and
in both cases I see keycodes, however in completely different styles. Here my
results:
1. showkey -k
Brightness on/off keycode 148
@mlmss: You should use showkey from console, not under X11 (KDE / GNOME /... )
Hit CTRL+ALT+F1
Next, log into system with you habitual login.
Now, you can use sudo showkey -s
At end, type exit, to logout, and ALT+F7 to go back on GNOME / KDE.
On my R60+, showkey work only on console.
--
@Andy: I have attached the dmidecode as asked.
I hope this helps. Thanks for your work.
Next, i will test your kernel.
** Attachment added: output of dmidecode for my Samsung R60+ (with latest bios
update)
http://launchpadlibrarian.net/21870978/dmidecode.R60P.txt
--
Samsung NC10
@Andy: I have tested your kernel
(linux-image-2.6.27-12-generic_2.6.27-12.28~lp295251apw1_i386.deb),
but this not solve the key release on R60P.
May be it's normal, because your waiting for dmidecode output.
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
I found some other bugs that related to Samsung laptop keyboard :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/212800
Samsung Q45
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/146710
Samsung Q45, RV700, Q210, R70, R60, R700
@Chris unfortunately there are no keycodes for wireless on/off, LCD
on/off and Monitor switch, however for brighness up/down there are also
no keycodes although they are working now. For speaker on/off and Volume
up/down there are keycodes so in general showkey -k was working.
@All has somebody
@mlmss: Can you check this file :
/usr/share/hal/fdi/information/10freedesktop/30-keymap-misc.fdi
Search for NC10: You should found this line :
match key=/org/freedesktop/Hal/devices/computer:system.hardware.product
contains_outof=NC10;SP55S;SQ45S70S;SX60P...
If not, search SP55S, and add NC10
@Cyril I followed your advice and added NC10 to the line you mentioned
(it was not there before) but nothing changed. Still now working
wireless on/off, LCD on/off and Monitor switch and still no keycodes
with showkey -k.
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing
Do you see any scancodes? Try running sudo showkey -s from a terminal
instead. If you see scancodes for those keys, what are they?
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because
@Andy I just installed your kernel on my NC10 with EasyPeasy 1.0 (orig. kernel
2.6.27-8). At the first glance everything works fine except of one big problem:
I don't have WLAN anymore (the atheros card is not found). Regarding the FN
keys, Brightness up/down are working as expected but
Your non-functioning keys is probably related to the hal-info fix that
hasn't been done yet, unless they worked before the kernel update.
Sorry, I had the intention of working on that bit but just haven't got
round to it yet.
** Changed in: hal-info (Ubuntu)
Assignee: (unassigned) = Chris
The R60P quirk is already in the latest version of hal-info in jaunty
and intrepid-proposed. The only missing quirk appears to be for the R70,
from a duplicate of this one.
mlmss - forget my last message, your NC10 already has the necessary
quirks. Could you switch to a console (CTRL+ALT+F1) and
For anyone running the R70S, I have a version of hal-info in my PPA to
test, alongside Andy's test kernel
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
@Cyril -- could you attach your dmidecode output please.
@All I have build some test kernels with the suggested patch applied.
Could those of you with NC10s test them and report back here. The
kernels can be found at the URL below:
http://people.ubuntu.com/~apw/lp295251-intrepid/
**
i´m on jaunty with 2.6.29 git kernel
if you apply hopkins given patch, then it will correct the problem, but NOT
entirelly
to have the brightness work without a problem on ubuntu :
1 : the hal fdi need to be modified so the brightness key are known
2: gnome-power-manager need to be patched
I would love to test the kernels but I am not experienced in this and not at
all confident about how to do it. If there were instructions on what to do then
I would gladly volunteers since I am very much interested in this problem to be
resolved.
thank you all for the hard work you are doing.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Andy Whitcroft (apw)
Status: Triaged = In Progress
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a
** Changed in: linux
Status: Fix Released = Confirmed
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux
Status: Confirmed = In Progress
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux
Status: In Progress = Fix Released
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have proposed a quirk for HAL for R60P keyboard. I'm waiting from
approval, but i attach the proposition if this can help.
I have the key release problem, but, the patch submited to the kernel mailing
list can't work for R60P
DMI_MATCH(DMI_PRODUCT_NAME, NC10)
For R60P :
Hi
I have the same problem with my Samsung R60+
I have updated my HAL file 30-keymap-misc.fdi according to this :
+ http://bugzilla.kernel.org/show_bug.cgi?id=11102
+
http://cgit.freedesktop.org/hal-info/diff/?id=f03aa98039195e5e2b6f0c70068af43fd9b5479d
This action have solved some hidden key
Any chance someone in the Ubuntu Kernel team could apply the patch to
the next Intrepid kernel, or do we need to wait for it to filter down
from upstream?
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug
** Changed in: linux
Status: Unknown = Confirmed
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The patch on the kernel bugzilla fixes the key release problem, I know
this as I wrote it. It fixes all of the key releases, allowing them to
be mapped by HAL correctly. There was mention of it being included in a
hotkey file (still can't find the page link)
As for the scancodes, there is an
Thanks for the info Stuart. All of those key mappings are already
present in hal-info for other Samsung models. All that is needed is just
another match rule added to 30-keymap-misc.fdi. Could someone with this
laptop please run lshal lshal.log and attach the log file.
Thanks
--
Samsung NC10
Here it is.
** Attachment added: Output of lshal on my NC10
http://launchpadlibrarian.net/20544732/lshal.log
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of
Thanks, that should do it.
** Changed in: hal-info (Ubuntu)
Status: Incomplete = Triaged
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs,
There is an additional problem, that the keys don't produce release
events. This is fixed by a kernel patch - see
http://bugzilla.kernel.org/show_bug.cgi?id=12021
The kernel team should probably take a look at this - once the release
event is in place then there are a number of easy ways to
I've added a kernel task and linked to the upstream bug report for the
missing key-release problem
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=12021
Importance: Unknown
Status:
I've got the scancodes for the brightness keys. For the other non-
working keys (battery / LCD / WLAN), could you please run:
tail -f /var/log/kern.log
...then press these non-functioning keys and post any output. If they
aren't being mapped to any keycodes, it would be good to know before I
It's a fault in how some of the Fn keys don't send the key release code,
making the OS think that the key is being held down. I have submitted a
patch to the kernel which fixes this issue, allowing the Fn keys
(including brightness) to be used properly.
For those who want to see the patch:
I think I saw a post on one of the HAL mailing lists showing that some
keycodes had been added. I can't seem to find it in google now (will
continue to have a look for it).
The battery key works on mine with gnome-power-manager, providing i
setup the scancode (which HAL should take care of). My
Until recently, the battery and WLAN keys weren't mapped to any
xkeysym's, and the battery key was also disabled in gnome-power-manager.
A recent update to xkeyboard-config and gnome-power-manager has
rectified this, and these keys should work as long as there are no other
issues with them
--
As it seems that at least part of the problem is due to the keys not
producing keycodes, I'm assigning a hal-info task, where a quirk can be
added to provide the correct scancode - keycode mapping.
** Changed in: hal-info (Ubuntu)
Sourcepackagename: gnome-power-manager = hal-info
Importance:
just to inform that i opened 2 bug report
one on kernel.org
and an other on Xorg
here is the link of the last one
http://bugs.freedesktop.org/show_bug.cgi?id=18590
because with acpi=off it worked, i opened first an acpi bug, but in
console mode (CTRL ALT F1 for example) the brightness work
On my NC10 the Brightness Keys are working, however, if i used them
once, the keyboard is completely dead and XFCE hangs (Menus are not
opening any more).
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug
I've tried to boot with acpi=off option on my intrepid kernel and I
encountered these problems on boot:
Frequency CPU scaling doesn't work anymore.
Wifi can't be powered-off yet.
Instead they're perfectly working:
Screen off key
Brightness UP/DOWN
--
Samsung NC10 brightness keys block keyboard
I installed Hardy (8.04.1) using the Alternate installer and I had to
use acpci=off as a boot option to install Ubuntu. I noticed that when I
used this boot option the brightness keys such as the up and down arrow,
but also the FN+F5 key worked as expected. Perhaps this info can help us
further
I made a typo in the description before.
Its not:
acpci=off
but
acpi=off
Sorry.
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is
can you share your solution please ?
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Doesnt look like somebody is interested in solving this ...
Thanks for nothing, other distris are much quicker than you.
I found a solution, so no need for you to look at this ... the few 10
owners will be happy with Win XP.
Good work.
I wish you good luck, you will need it.
--
same problem here.
i first through it may be an acpi problem, because when i add acpi=off in
grub, the brightness worked
after some search i found out that the keys were not mapped, so i did a
setkeycodes e008 225
setkeycodes e009 224
in console (CTRL+ F1-F6) it work normaly
but in graphical
maybe this can help you guys, at least i hope so :
i killed gnome-power-manager and run it this way
gnome-power-manager --no-daemon --verbose
i pressed the decrease button ONCE and then the increase button ONCE (because
the brightness was at 0%)
then i switch to console and back in graphic mode
I have the same problems with the fn-keys, which were written above... I
hope that these problems will be solved.. thx
--
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
https://bugs.launchpad.net/bugs/295251
You received this bug notification because you are a
I have the same problem.
But maybe this helps:
I also set the keymaps Andreas already described. After an X restart i´m able
to use the brightness keys and the keyboard gets stuck.
But i can still switch to a console with the ALT+CTRL+F1-F6 keys. After
switching back to X with CTRL+ALT+F7 i am
Hi edufl13
as a workaround you can use:
sudo apt-get install gconf-editor xbacklight
gconf-editor
apps - metacity global_keybindings
assign
run_command1 AltF11
run_command2 AltF12
or any keys you want.
apps-metacity-keybinding_commands unter
assign
command_1 xbacklight -dec 10
command_2
95 matches
Mail list logo
