synaptics and compiz not compatibles

[mabovo]

Binary package hint: compiz

Trying to configure tap buttons in synaptics with desktop effects enabled on a MacBook 2nd generation touchpad gets completely different results following tips described in https://help.ubuntu.com/community/MacBook

[mabovo (mabovo)]

Here is a crash report from compiz when I was reconfiguring xorg.conf to tune up synaptics in Hardy 8.04 kernel 2.6.24-4

[mabovo (mabovo)]

It is very hardy to use touchpad without an appropriate xorg.conf in Hardy 8.04

[mabovo (mabovo)]

Synaptics touchpad works perfect when desktop effects are disabled.
When certain plugins are enabled and have more than two windows to switch from desktops the effects of Compiz conflicts with touchpad tap buttons.
Maybe there are others Compiz plugins that conflicts with Gsynaptics I didn't test others.

[Chris Halse Rogers (raof)]

Thank you for reporting this bug, and for trying to help make Ubuntu better. However, your report does not have enough details for us to do anything about the problems you have described. Could you please add the following information:
* The specific steps or actions that you took to try to change your trackpad behaviour. Did you try changing anything in gsynaptics (System->Preferences->Touchpad)? If so, what did you try?
* The "completely different" results you got when following the Mac Book instructions - what happened that you didn't expect?
* What Compiz plugins did you find interfered with your trackpad? How did the behaviour change when you had more than 2 windows on the screen with compiz active?

You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.

Additionally, this seems to be specific to your hardware. My laptop has a synaptics touchpad, and have never seen any bad interaction between Compiz and gsynaptics.

[Bryce Harrington (bryce)]

Marking xorg component invalid since sounds like it's a gsynaptics/compiz conflict.

[Bryce Harrington (bryce)]

Marking -intel component invalid since it clearly isn't a video driver issue.

[mabovo (mabovo)]

What I did was creating more than three desktop areas in my laptop and set plugin desktop wall enabled in Compiz.
Elsewhere I set Option "HorizTwoFingerScroll" "1" in xorg.conf.
When I scroll two fingers horizontally on display screen the desktop area change from working space 1 into desktop area 3 or 4 or 2, for instance, like mouse movements with left button pressed. This action generates a conflict between Compiz and gsynaptics of windows out of control.

[Chris Halse Rogers (raof)]

That is expected behaviour: the vpswitch compiz plugin makes mouse scrolling over the desktop change the viewport. Or does this occur when you use mouse scrolling over an application window?

Is this the only unexpected behaviour?

[mabovo (mabovo)]

You sure, this happen only in touchpad, mouse scrolling works correct.

[Chris Halse Rogers (raof)]

Just to confirm: the behaviour you are seeing is that when you "two finger scroll" on the desktop it changes your viewport. Does this happen when the mouse pointer is over a window (not over the desktop?).

[mabovo (mabovo)]

Yes, using "two finger scroll" over between windows pass trough the desktop.

[mabovo (mabovo)]

I'm getting a more manageable desktop environment on MacBook after changing some parts of xorg.conf mainly in synaptics server.

[Michele Mangili (mangilimic)]

Hi!

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Robert Ancell (robert-ancell)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!