This release has reached end-of-life [0].
[0] https://wiki.ubuntu.com/Releases
** Changed in: linux (Ubuntu Hardy)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/217504
** Changed in: debian
Status: New => Fix Released
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
acpi-support is deprecated, and acpi_fakekey is not going to be fixed.
Hotkey synthesis should always happen within the Linux kernel instead.
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: acpi-support (Ubuntu)
Status: Triaged => Won't Fix
--
acpi_fakekey
Sorry, I don't have the time to keep the patch up to date and it is my
understanding that most multimedia keys are be handled by the kernel at
this point, so this should be largely unnecessary.
The patch for 0.115 is still available at
http://launchpadlibrarian.net/21350541/acpi-
support_0.115_0.
@Tom Jaeger
Tom, could you make a separate patch for acpi_fakekey for 9.04 though
the acpi bag is fixed but fake_key is not working
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bu
Thanks for the information.
I will pursue the Zoom key issue at #267682.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
On Fri, Mar 06, 2009 at 07:08:56AM -, Thomas Hood wrote:
> In Jaunty (4 March 2009), xev can now see the ThinkVantage keypress on
> my ThinkPad X61 and the ThinkVantage key can be assigned as a keyboard
> shortcut in GNOME.
> However, the Zoom key (i.e., Fn-Space) is still not seen by xev.
Co
In Jaunty (4 March 2009), xev can now see the ThinkVantage keypress on
my ThinkPad X61 and the ThinkVantage key can be assigned as a keyboard
shortcut in GNOME.
However, the Zoom key (i.e., Fn-Space) is still not seen by xev.
acpi_listen can see both ThinkVantage and Zoom:
$ acpi_listen
ibm/ho
** Changed in: acpi-support (Ubuntu)
Sourcepackagename: linux => acpi-support
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
The ThinkVantage key works in Jaunty (4 March 2009) on a ThinkPad X61.
Ref:
http://www.thinkwiki.org/wiki/Installing_Ubuntu_8.10_(Intrepid_Ibex)_on_a_ThinkPad_X61#ThinkVantage_key_not_seen_by_X
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You receiv
acpi_fakekey is just broken, it's just unreasonable to send a key to a
random keyboard device and expect that the kernel will let the event
though the key isn't actually present on the keyboard.
If we decide to keep acpi_fakekey around, I think we should switch to
uinput to get rid of these issues
** Tags added: regression-release
** Tags removed: cherry-pick regression-potential
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
I just debugged the very same issue in bug 268429, and got to the same
result. acpi_fakekey opens the right device and writes to it, but
nothing happens for e. g. "150" (KEY_WWW).
As written in https://wiki.ubuntu.com/AcpiSupportDeprecation, we can
either fix the kernel to convert *all* ACPI hotke
I've confirmed with the original submitter that the hotkey in question
now works for him in jaunty, without the need of acpi_fakekey working;
the linux task here is therefore either invalid or fixed.
acpi_fakekey itself, as well as all of acpi-support, is deprecated. If
you are having problems wi
I'd like a bit of clarification:
What needs to be done to solve this bug? An in-kernel driver?
Is there some work being done for that or is it waiting for someone to start?
Why does the proposed patch is not released until the 'perfect' solution is
ready?
--
acpi_fakekey stopped working for cert
I've got ASUS A6B00U notebook (from A6U series). This is an issue for me.
OS: Hardy Heron 8.04.1
Kernel: 2.6.24-22-generic
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which
Steve Langasek wrote:
> acpi_fakekey (and acpi-support itself) is considered deprecated; mapping
> acpi events to input events should be handled by an in-kernel driver
> instead.
And until that happens we have a perfectly viable alternative using
uinput. Just saying.
> Who has the original keyboa
acpi_fakekey (and acpi-support itself) is considered deprecated; mapping
acpi events to input events should be handled by an in-kernel driver
instead.
Who has the original keyboard with the KEY_WWW problem? Is this still a
problem in Ubuntu 8.10? If so, please provide information about your
lapt
I cannot see anything insecure in the way acpi_fakekey works. After all,
it's a root-only feature.
More than that, 'setkeycodes' allows to achieve similar results to my
proposed patch by mapping a wild guess keycode to the wanted keys.
However, the solution is not portable, because it requires a k
It IS kernel incompatibility, but the kernel behavior is correct.
Rather, the scripts were using unsafe (in terms of security) methods for
generating fake keys.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because
Does not seem to be a kernel issue.
** Changed in: linux (Ubuntu)
Importance: High => Undecided
Assignee: Tim Gardner (timg-tpi) => (unassigned)
** Changed in: linux (Ubuntu Hardy)
Importance: High => Undecided
Assignee: Tim Gardner (timg-tpi) => (unassigned)
Status: Triage
I've posted a debdiff in the other bug report:
https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/59695/comments/626
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, w
I confirm this package solve the issue with an asus f3sv.
Thanks a lot!
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Hi Tom!
Thanks. Great job !!!
Now almost everything works fine, except two volume keys. But they produce no
acpi events at all.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs
Tom Jaeger wrote:
> Packages will appear in my PPA in about 20 minutes.
Updated packages (+ppa3) are here:
http://ppa.launchpad.net/thjaeger/ubuntu/pool/main/a/acpi-support/
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notifica
After manually loading uinput, acpi_fakekeyd sucesfully started, volume
keys *do* work, as well as the "Access IBM" key, that didn't work before
(with intrepid's version of acpi-support). So it seems to work for me!
Thank you, I will use this as a workaround until it is ready to become
an official
Thanks. So the uinput module isn't automatically loaded in a default
ubuntu installation. I've modified the postinst script now to load
uinput if necessary add uinput to /etc/modules if it's not already
there. Is that the right way to do it (it's how thinkfinger does it) or
should I have the dae
Congratulations to me for copy-ing wrong (and even stupidly wrong) command (and
appending the correct response). The first line should have been:
[EMAIL PROTECTED]:~$ sudo ps aux | grep fake
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You receive
@Tom:
[EMAIL PROTECTED]:~$ sudo -i acpi_fakekeyd
matija 22840 0.0 0.0 3236 808 pts/0S+ 22:51 0:00 grep fake
[EMAIL PROTECTED]:~$ which acpi_fakekeyd
/usr/bin/acpi_fakekeyd
[EMAIL PROTECTED]:~$ sudo acpi_fakekeyd
open: No such file or directory
--
acpi_fakekey stopped working for
lujana, do you see acpi events if you press those keys while running
"sudo acpi_listen"?
Matja, that's strange. Can you check if acpi_fakekeyd is even running?
If not, what's the output of "sudo acpi_fakekeyd?
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/
Thanks for your effort, Tom.
Sorry to bring you bad news, but I have tried your (i386) acpi-support
package on my Thinkpad R52 (where most keys work on Intrepid, but
"Access IBM" key doesn't), but after installation at least the volume
buttons ceased to work too (don't even show up on xev). I trie
Hi Tom!
I have tried your acpi package on Sony Vaio-TX2. Unfortunately, i have
seen no difference with additional keys. Xev showes nothing.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of U
I've added an updated acpi-support package to my PPA that should fix
this issue regardless of the kernel used. It splits up the work that
acpi_fakekey is currently doing into an acpi_fakekeyd daemon that
creates a uinput device and then listens for input on a fifo and an
acpi_fakekey frontend that
On Mon, Nov 24, 2008 at 11:31 PM, Bryce Harrington <
[EMAIL PROTECTED]> wrote:
> Hi Tom,
>
> There isn't really an upstream for this package - it's maintained
> entirely by Ubuntu (and Debian). If you can get a working patch, then
> you just need one of the Ubuntu engineers to incorporate it for
Hi Tom,
There isn't really an upstream for this package - it's maintained
entirely by Ubuntu (and Debian). If you can get a working patch, then
you just need one of the Ubuntu engineers to incorporate it for you.
I'd be happy to do this when you're ready with a patch - just ping me on
IRC.
--
a
Okay, so acpi_fakekey just looks for a random input device that it
thinks is a keyboard and then sends the key to it. This is wrong, and
patching the kernel is not the solution. The proper way is to go
through uinput. But there are two problems: First, single key uinput
devices are detected as
** Changed in: linux (Ubuntu Hardy)
Status: Confirmed => Triaged
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
This bug seems to have been reported again for Intrepid here:
https://bugs.launchpad.net/bugs/267682.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
truly I'm quite tired of keeping this package update, kernel team release a new
version every 2 weeks and this patch isn't included yet, I'm really pissed off
about this behaviour.
I give up and I keep the bug on my system too, just to explain that this is not
the case where I've the package and
MarcoBazzani, would you be able to use Sergey Yanovich patch on the
latest Hardy Heron linx kernel (linux-
image-2.6.24-19-generic_2.6.24-19.45ubuntu1_i386.deb) and upload it
since the latest patch you have released is on linux-
image-2.6.24-19-generic_2.6.24-19.36ubuntu1_i386.deb and the
2.6.24-19
it will not be fixed increasing the kernel version number but removing
the check of keys provided by a keyboard
or rewriting acpi_fakekey
:)
cheers
Marco
On Thu, Aug 28, 2008 at 6:03 PM, Leann Ogasawara <[EMAIL PROTECTED]> wrote:
> The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel
I can confirm, this is still broken in the 2.6.27 kernel.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Hmm, here's a thought: aren't the "uinput" framework and module meant
exactly for this purpose (injecting input events)? Perhaps acpi_fakekey
can be adapted to use uinput instead of writing to existing input
devices.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net
since it's considered a feature and not a bug it will be difficult that this
patch will be included in the mainline kernel
maybe there is better way to reproduce this kind of signals for example
registering a fake input device
--
acpi_fakekey stopped working for certain keycodes
https://bugs.la
It looks like this will not be fixed in kernel 2.6.27 either because (at least
up to rc3) the section of drivers/input/input.c in Sergey Yanovich's patch
isn't going to change. I believe acpi_fakekey is only a Debian-based distro
thing, so has anyone from Debian or Ubuntu even tried to argue tha
This is also still broken in the latest Intrepid kernel,
2.6.26-5-generic.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
I've got events coming through on acpi_listen but acpi_fakekey isn't
working even after an attempted setkeycodes hack... any ideas, anyone?
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ub
The keys do generate acpi events, but the events call scripts which use
acpi_fakekey, and that is what does nothing.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
this patch doesn't fix broken keys of brightness, if your buttons doesn't
generate acpi events this patch is useless
run
tail -f /var/log/acpid
and press your brightness buttons and see if some kind of events are generated
(for me brightness works also without the patch)
--
acpi_fakekey stoppe
Could anyone tell me how to assign the (presumably fixed) keys to
brightness control?
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
patched 2.6.24-20
** Attachment added:
"linux-image-2.6.24-20-generic_2.6.24-20.37ubuntu1_i386.deb"
http://launchpadlibrarian.net/16278254/linux-image-2.6.24-20-generic_2.6.24-20.37ubuntu1_i386.deb
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
Y
@MarcoBazzani: Yes I know. Thank you for the patch ;)
@Stas: For example https://help.ubuntu.com/community/MultimediaKeys
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which
to MarcoBazzani
how to associate them ?
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
On Tue, Jul 22, 2008 at 9:28 PM, Pepe <[EMAIL PROTECTED]> wrote:
> Work for me with xev:
>
> KeyPress event, serial 31, synthetic NO, window 0x301,
>root 0x59, subw 0x0, time 534081, (-289,312), root:(305,336),
>state 0x0, keycode 130 (keysym 0x0, NoSymbol), same_screen YES,
>XLooku
Work for me with xev:
KeyPress event, serial 31, synthetic NO, window 0x301,
root 0x59, subw 0x0, time 534081, (-289,312), root:(305,336),
state 0x0, keycode 130 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEven
On Tue, Jul 22, 2008 at 1:32 AM, josh04 <[EMAIL PROTECTED]> wrote:
> Me neither, also on hardy.
>
> --
> acpi_fakekey stopped working for certain keycodes
> https://bugs.launchpad.net/bugs/217504
> You received this bug notification because you are a direct subscriber
> of the bug.
>
strange I've
Me neither, also on hardy.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
Patch presented by MarcoBazzani don't work for me.
P.S. ubuntu hardy
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
On Mon, Jul 21, 2008 at 7:00 PM, Tim Gardner <[EMAIL PROTECTED]> wrote:
> @MarcoBazzani: It would be useful if you would attach the patch against
> -19.36 that you used to produce your binary package.
>
> --
> acpi_fakekey stopped working for certain keycodes
> https://bugs.launchpad.net/bugs/21750
@MarcoBazzani: It would be useful if you would attach the patch against
-19.36 that you used to produce your binary package.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, whic
for who is interested here there is a deb of -generic i386 patched
** Attachment added:
"linux-image-2.6.24-19-generic_2.6.24-19.36ubuntu1_i386.deb"
http://launchpadlibrarian.net/16203183/linux-image-2.6.24-19-generic_2.6.24-19.36ubuntu1_i386.deb
--
acpi_fakekey stopped working for certain
@unggnu
where is the patch ?
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
This is still an issue in Intrepid. The patch works fine in Hardy and
Intrepid and is a one-liner so what prevents it from being integrated or
sponsored? Or are there plans to make acpi work with the new kernel
code?
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/
make some tests of a bunch of different installalation of hardy on
laptops and desktops I can confirm this bug
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Hardy)
St
The problem still appears with 2.6.26 Vanilla Kernel.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
** Changed in: debian
Status: Fix Released => New
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
same problem here I can confirm
fakekeys > 100 doesn't works
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Same problem on my Asus Z92J (also A6J), with xubuntu 8.04.1.
There is three key that doesn't work (and which works with 7.10) : the
WWW key, the eject key, and the "Power4Gear" key, which start
/etc/acpi/lockbtn.sh.
I have also noticed that the keycode send via acpi_fakekey is not the
same than
** Changed in: linux (Ubuntu Hardy)
Importance: Undecided => High
Assignee: (unassigned) => Tim Gardner (timg-tpi)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Target: ubuntu-8.04.1 => None
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launch
Btw. does anyone know why the kernel developers have changed this
behavior? There have to be a reason. Is there any upstream bug report?
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubunt
I can confirm that the sony eject button works fine again with Sergey
Yanovich patch. It would be great if this could make it into Hardy
8.04.1.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member
Is this bug somehow related to this one
https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/211952 ?
"sudo setkeycodes e076 148" makes WOW-Video button visible, so I can map
it to action I want.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
Y
The fix in Debian is described as follows, in acpi-support 0.109-1 (not the
kernel):
* Divert sleep button to sleep.sh if power management daemons are not
running, for thinkpad, panasonic, sony and toshiba laptops.
Closes: #467374, 373660.
I guess that does not make acpi_fakekey work
FYI
The CD eject button (and others) on my Sony Vaio VGN-A270P work fine in
7.10. They do NOT work in 8.04! Something (obviously) broke sonypi
(I'm guessing). Running xev on 7.10 (clean install) gets the following
when pushing the eject button:
FocusIn event, serial 30, synthetic NO, window 0x
** Changed in: debian
Status: Fix Committed => Fix Released
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
> Tim, it looks like a local commit to Sergey's private repository. Is
that correct, Sergey?
That's correct. I don't an exported kernel repository, only my local
tree.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification b
** Changed in: debian
Status: Unknown => Fix Committed
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Tim, it looks like a local commit to Sergey's private repository. Is
that correct, Sergey?
** Bug watch added: Debian Bug tracker #373660
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373660
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373660
Importance
Daniel - in what tree does this cherry-pick exist?
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Tim Gardner (timg-tpi)
Status: Triaged => In Progress
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You
Milestoning for 8.04.1, because the patch from Sergey appears to fix
this regression, which breaks acpi-support in different ways (its
invoked actions get discarded).
** Changed in: linux (Ubuntu)
Target: None => ubuntu-8.04.1
--
acpi_fakekey stopped working for certain keycodes
https://b
Thanks to balleyne and Benhamin Braatz the thinkvantage key is
recognized by the keyboard shortcuts gui.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
@Victor: /etc/rc.local and /usr/share/hotkey-setup/ibm.hk are both only
executed at boot time. So you would have to reboot to see the effect of
changes there.
But you can also execute "sudo setkeycodes e017 148" in a terminal for
an immediate result.
It does not really matter if you use ibm.hk or
@VictorGreen: You can add that line anywhere to the file (ibm.hk), as
long as it's on a separate line. I'm not sure what exactly needs to be
restarted in order to make it work (especially since it says the bug is
in the kernel, as it works with 2.6.22), but I waited until I restarted
my whole machi
Where do I add the setkeycodes e017 148? Philippe Seewer said /usr/share
/hotkey-setup/ibm.hk and christian said /etc/rc.local. I tried adding
the code to the first suggested file, but didnt know where so I stuck it
in at the bottom.
The command: "xbindkeys --key" still showed no input from repeat
mmm. I'm not happy with the fix (setkeycodes e017 148). The fix
seems to conflict with Fn+F8 (touchpad on/off). After running
setkeycodes e017 148 the ThinkVantage button is producing the same
keycode as the Fn+F8 combination. For helping troubleshooting I attach
the output of showkey:
sho
@Seth: ditto for me
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
I will second Philippe Seewer's fix. I added it to my T61 and my
ThinkVantage button is working again.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I can confirm that adding the line
setkeycodes e017 148 (for the ThinkVantage button)
and
setkeycodes 0082 192 (for the Fn+SPACE combination)
to /etc/rc.local is working for me on my LENOVO, ThinkPad R61, 8943DMG
with Ubuntu 8.04.
Not nice, but it works.
--
acpi_fakekey stopped working for
I can confirm that adding the line
setkeycodes e017 148
to '/usr/share/hotkey-setup/ibm.hk' fixes the 'Access IBM' button on my
T42p.
I can confirm as well that showkey and acpi_listen show the button, but
without the setkey fix the event isn't propagated through to X via
acpi_fakekey.
Interes
** Tags added: cherry-pick
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
Will this get in to Hardy before release?
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Hi guys, I've recently submitted a bug, which was marked as a duplicate
of this one (see #218333). However, there are some minor differences,
eg. I'm running kernel 2.6.22.14-generic (uname -r, fresh install of
Kubuntu CD), and my keys are recognized by HAL, no error can be seen in
dmesg output, qu
Hmm, looks like you got it.
I was starting to think the kernel was doing some kind of check to see if the
key being read was the actual key being triggered, but I couldn't figure out
how the kernel would know since all events go through the device file one way
or another.
And it seems it was ju
Since August 2007, kernel input handler checks that a triggered key is
reported as present by keyboard. This patch should restore all types of
acpi_fakekey related regressions.
** Attachment added: "Drop keycode bitmap check in input events"
http://launchpadlibrarian.net/13530068/fakekey.patch
I am experiencing similar behavior with debian/unstable on Sony TX770P
laptop. Ubuntu bug 187980 looks a duplicate of this one. Debian 373660
also addresses the same problem.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notifica
Interestingly enough, when I manually define the keycode using setkeycodes (in
my case, the IBM button is e017 on a T40p) the key magically works.
However, it seems that it's dependent on each other. The key isn't recognized
until both the kernel has it defined, and the key is triggered through a
Tested. It detects my keyboard fine, but still doesn't work. The format
doesn't appear changed, either. No errors from writing to the device
file. Moreover, standard keys still work through acpi_fakekey, so for
some reason or another, the kernel is deciding that extraneous keys are
ignored (what th
On my Samsung P35 the most important key not working is KEY_VIDEOOUT (227)
I'm using kernel 2.6.24.16.18
Using the previous comments maybe the input mapping is relevant:
[ 11.855577] input: Macintosh mouse button emulation as
/devices/virtual/input/input0
[ 11.902929] input: AT Translated Set
Additional note.
The problem would have been caused by the kernel somehow changing the order of
the devices, and one of them is being incorrectly detected as a keyboard.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification
1 - 100 of 103 matches
Mail list logo
