Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#17607 - [hal] synaptics settings ignored after hal upgrade

Attached to Project: Arch Linux
Opened by Emmanuel (bkk_drs) - Saturday, 26 December 2009, 11:37 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 08 June 2010, 13:42 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: synaptics settings are ignored after hal upgrade - touchpad behavior falls back to default (no cursor speed settings, no scrolling)


Additional info:
* package version(s)
hal 0.5.14-1


Steps to reproduce:
use latest hal 0.5.14-1, downgrading solves the issue.
   xorg.conf (1.2 KiB)
   11-x11-synaptics.fdi (0.9 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 08 June 2010, 13:42 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Won't fix input hotplugging bugs in hal anymore, as xorg-server 1.8 uses udev.
Comment by Jan de Groot (JGC) - Saturday, 26 December 2009, 15:31 GMT
Can you attach the output of lshal?
Comment by Emmanuel (bkk_drs) - Saturday, 26 December 2009, 16:28 GMT
sure. output is attached.

edit: this is with 0.5.13-3
   lshal.txt (149.7 KiB)
Comment by Jan de Groot (JGC) - Saturday, 26 December 2009, 16:40 GMT
Can you also attach the output of 0.5.14?
Comment by Emmanuel (bkk_drs) - Saturday, 26 December 2009, 16:42 GMT
attached
   lshal_fail.txt (149.9 KiB)
Comment by Jan de Groot (JGC) - Saturday, 26 December 2009, 16:51 GMT
I think this is a regression caused by this commit:
http://cgit.freedesktop.org/hal/commit/?id=52e039f3b0a5749f706b97491087b9632d30512f

What happens here is that hal doesn't assign the input.touchpad property anymore. I don't know if this is a bug in hal or something not reported correctly to hal. You can fix this by assigning input.touchpad yourself using an extra ruleset. This is also done for ETPS/2 touchpads in the fdi file included in the synaptics driver. You might want to duplicate the rule for now and change the ETPS/2 string to something that matches your touchpad.
Comment by Jan de Groot (JGC) - Saturday, 26 December 2009, 17:08 GMT
I see the workaround isn't needed for ETPS/2 anymore though.
Could you paste or attach the output of this command?

udevadm info --query=property --path=/sys/devices/platform/i8042/serio4/input/input7/event7
Comment by Emmanuel (bkk_drs) - Saturday, 26 December 2009, 17:11 GMT
That did the trick, thank you very much Jan.

[OT]Jan, your knowledge, reactivity and dedication are incredible (from what I have seen over the years). Just wanted to say it. Thank you.[/OT]
Comment by Emmanuel (bkk_drs) - Saturday, 26 December 2009, 17:14 GMT
udevadm output attached.

as mentioned above, the rule to assign input.touchpad solved the issue.
   udevadm.txt (0.3 KiB)
Comment by Jan de Groot (JGC) - Saturday, 26 December 2009, 18:07 GMT
Hmm, this is weird, according to udev your mouse is a keyboard device. I don't see how hal can cause these changes, as these properties are set through udev.

Loading...