Description of problem:
I'm using Mageia 2 beta 3 on my HP 630 notebook. It has a Synaptics touchpad with a hole in the top-left corner. When I tap it twice, the LED above starts lighting and the touchpad is disabled (http://i.imgur.com/VUIKZ.jpg). It's the normal behaviour on Windows.
I've found that preinstalled SuSE Enterprise Desktop 11 distro supports this function too, but when I deleted it and installed a standard SLED 11 version, it doesn't work at all.
However, there are a patch for Synaptics drivers which enables function I described: https://github.com/perusio/xorg-synaptics-led-support
To use this patch I would have to comple a kernel from sources. Is it possible to make a package from this patch, which will be available on the repository?
Steps to Reproduce:
1. Turn on Mageia 2 beta 3 with touchpad on.
2. Tap twice on the hole in the top left corner of touchpad.
3. Touchpad is still enabled, LED doesn't light.
This bug was filed against cauldron, but we do not have cauldron at the moment.
Please report whether this bug is still valid for Mageia 2.
Yes, it's still valid for Mageia 2.
Sorry, just forgot about this one, will take a look in the next few days. Daniel, please ping me again here if nothing happens until next weekend, OK?
Sure, I will. :)
I've been asked to remind you, Florian, about this bug. So do I. :)
Sorry, was totally swamped with forum support. Will try to get back to it during this week. If you don't get any reply until next weekend, please ping me again afterwards.
It's weekend, just ping you, Florian.
Florian, are you still alive? :) This feature will be really great - my touchpad is big and it's easy to touch it accidentally while typing. It would be great if you could help. Thanks in advance. :)
Yes still alive :/
Had a closer look, it needs a patch against the kernel. Will have to talk to our kernel guy, if we can add this or if we already have this patch or if we can add it. Then we'll have to wait for the kernel with that patch, and then the patch against synaptics module is effective.
Ok, so Thomas will include the kernel patch in the next kernel updated candidates for Mageia 2 and cauldron, then i'll add the patch to synaptics driver. So if i forget, and you get a kernel update for Mageia 2, then scream for me again :)
Sure, thanks. :) What's estimated time of this kernel update release? A month, two, more?
Ahh, crap, i knew i forgot to ask something important :)
Maybe more coming weekend or so ...
There is now kernel-3.3.8-1.mga2 in updates_testing with the patch applied
Daniel could you please test with the new kernel, you can comment either here or on bug 6914.
Sure. How can I install it? Which media source I have to enable?
No need to test, as i still need to patch the synaptics driver itself :/
Gotten around to patch synaptics driver, but i'm not quite sure if that is still effective, as the original patches are against kernel 2.6.28 and synaptics driver 1.4.
But please test, x11-driver-input-synaptics-1.5.0-5.mga2 packages should soon be available from your favorite mirror in core/updates_testing and then report back here.
So I should install x11-driver-input-synaptics-1.5.0-5.mga2 only, or within kernel-3.3.8-1.mga2?
I've installed kernel-3.3.8-1.mga2 and then x11-driver-input-synaptics-1.5.0-5.mga2, both from updates_testing.
Next, I've restarted my laptop and choose new kernel in GRUB menu.
I see two new variables in synclient, but neither LED and turning touchpad off by double click on the top-left corner doesn't work.
I've mailed some other packagers who are a bit more into this driver, hopefully they can help. Problem is that the patch was against an older version of synpatics driver, and some code changed in between, so the patch may need to be rewritten and adapted to new code, but i'm no coder, so i can't help with that.
This patch has been rewritten then dropped by its upstream author due to issues.
So I don't see any way we can apply it as it:
"- Drop broken LED double-tap patches (bnc#768506,bnc#765524)"
You may look at new version announces in order to check if there was any fix regarding your issue:
@Thierry: Thanks for the comment ...
Reassigning to bugsquad, nothing more i can do here ...
This bug was reassigned to bugsquad, so setting status back to NEW.
Any hacker who wants to take this bug: feel free to assign it to yourself
Closing as old since nothing happened around this bug report in the last 4 years. Reopen in needed.