Hi Julien, On Fri, Sep 05, 2008 at 03:33:45PM +0200, Julien Cristau wrote: > On Fri, Sep 5, 2008 at 15:05:33 +0200, Micha Lenk wrote: > > > You find attached my xorg.conf in two versions: The one which was the > > result of the upgrade (.double-click-with-lenny suffix) and the fixed > > one that finally works here (.works-with-lenny suffix). > > > > If I remember correctly the second pointer was necessary because the > > touchpad didn't generate events on /dev/input/mice with the kernel in > > Lenny (2.6.24-6~etchnhalf.4). Now the touchpad also generates data on > > /dev/input/mice, so I suppose the additional pointer section in > > xorg.conf should have been removed by the xorg upgrade to Lenny. > > > I don't understand how dexconf could have generated such an xorg.conf, > with two devices using the mouse driver. But, it looks like a lot of > people are having this problem, so maybe there's something I'm missing. > What's even weirder is how your device is named 'Synaptics touchpad' yet > has 'Driver "mouse"'. Are you sure it hasn't been manually modified?
I've just checked from my backup files and need to say that I was not able to generate an xorg.conf by using dexconf that contains this extra mouse device. So probably my local configuration really was modified manually. I guess I found a workaround somewhere in the lazyweb suggesting the additional mouse device. Just to make sure: How can I definitely confirm that my backed-up xorg.conf has been manually modified? Please let me know if I can check/try/do something else with my backed-up files/configuration. > Also, I'm pretty sure every mouse device, unless otherwise grabbed, > *does* produce events on /dev/input/mice on all 2.6 kernels. > > In any case, I'll gladly accept patches (bonus points if they're > tested). Do you have an idea how to tackle this? Would it be sufficient to alert the user if he has ended up with two mouse devices in a manually changed xorg.conf? I have no idea what fits best here... Regards Micha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]