On 07/06/07, Ortwin Glück <[EMAIL PROTECTED]> wrote:
> i've followed the instructions on your site
As if that's a guarantee for anything :-) I am just describing my setup
there. There's always room for improvement.
hahahh. to be honest, i was under the impression that what you posted was a
method to actually get the touchpad to work properly (IE: with synaptics)
after resuming. do you experience the same behaviour as i do, or does your
touchpad work "properly" after resuming?
to
> have X use /dev/input/touchpad which is setup as a symlink to the proper
> input device. however, upon resuming, X is unable to open
> /dev/input/touchpad , and thus synaptics isn't used:
The question is *why* can it not open the device. If the device node is
not present, then we must notify X over dbus as soon as the device is
available. Using dbus-send probably.
If however the device is present but the open fails, I don't know what
to do.
i'll try to make some time over the weekend to post to an Xorg/dbus/udev
mailing list and ask from some tips/help. which one(s) do you recommend i
approach? i know virtually nothing about dbus and udev, so am not even sure
which is the appropriate one to approach.
-Nick
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Mactel-linux-users mailing list
Mactel-linux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mactel-linux-users
