I'm using a fresh install of Hardy-KDE4. There's only 1 keytouchd_launch file in /etc/X11/Xsession.d, not 2. Disabling this in /etc/X11/Xsession.options left me with a desktop that finally shuts down properly, but the extra keys were not working.
I put a symlink to keytouchd into my KDE4 autostart folder and now it works as expected - exactly 1 keytouchd process (instead of 4) that doesn't block session termination.
I don't think this is the intented way to invoke keytouchd. The changelog mentions keytouchd-launch and dbus. How is this expected to be handled? The hints in the keytouchd-launch manpage are rather vague.
I'm using a fresh install of Hardy-KDE4. There's only 1 keytouchd_launch file in /etc/X11/ Xsession. d, not 2. Disabling this in /etc/X11/ Xsession. options left me with a desktop that finally shuts down properly, but the extra keys were not working.
I put a symlink to keytouchd into my KDE4 autostart folder and now it works as expected - exactly 1 keytouchd process (instead of 4) that doesn't block session termination.
I don't think this is the intented way to invoke keytouchd. The changelog mentions keytouchd-launch and dbus. How is this expected to be handled? The hints in the keytouchd-launch manpage are rather vague.