Search:

To find the touchpad udi use this command:

hal-device |grep Synaptics -B 9|grep udi
the output should be like this:

35: udi =...

Right FokkerCharlie! Don't worry :)
Once you set a name for the touchpad in the touchpad.fdi file you can configure the right device using gpointing-device-settings instead of gsynaptics.

PS:...

I found a patch for syndaemon that allow us to specify the target device.
http://bugs.gentoo.org/show_bug.cgi?id=282949#c1
http://bugs.gentoo.org/attachment.cgi?id=202431&action=view
Great thanks...

With karmic the target of syndaemon and synclient are the media keys instead of the touchpad.

I can't solve this problem with these methods...

See here :)
http://ubuntuforums.org/showthread.php?p=7535907#post7535907

One love

You need to write a /etc/hal/fdi/policy/touchpad.fdi file like this.

<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="info.udi"...

After an update from intrepid to jaunty xfmedia won't run.

$xfmedia
Segmentation fault
$dmesg|grep xfmedia
[ 2608.836874] xfmedia[15172]: segfault at 726f78 ip b75d69e0 sp bff448b4 error 4 in...

Very good howto :D
I will merge it with the one I wrote some time ago ;)
Done ;)

One love

I suspect you are using a wrong lircd.conf. Try to create your own lircd.conf with

irrecord

One love

I suspect it is a problem with maximized windows related to compiz.
Two days ago I unchecked the "Snapoff maximized windows" box in Move Window plugin and the "Ignore hints when maximized" in...

These steps had successful results under intrepid, both 32 and 64 bit, I didn't tried with hardy.

1 ~ Type

hal-device|grep -i wec
output should be

57: udi =...

Yesterday i had the cir working! :D
You need to build and install lirc from the latest cvs.
In this discussion you can find some other details.
Sorry for bad english

One love