[regression] shipped mousetweaks (3.0) does not work with shipped control-center (2.32), needs downgrade

[Jools Wills]

There's a version mismatch between mousetweaks and gnome-control-center + gnome-settings-daemon. The GNOME 3 versions of these modules use dconf for configuration and the 2.32 versions use gconf. Downgrading mousetweaks to 2.32 will fix this.

Original description:
First of all I can currently unable to get "simulated second click" in gnome assistive technologies to work at allw ith the unity desktop - ie i cannot hold the left button and simulate a second click. Secondly, as a click and hold is already being utilised to move entries in the unity menu, how should this interact with this accessibility option. take for example a single click touchscreen.

[Jools Wills (jools)]

sorry for the typos. should read "I am currently unable" etc.

This is Unity on Natty beta 2.

[Alistair Buxton (a-j-buxton)]

Confirmed. Dwell click doesn't seem to work either.

[Jools Wills (jools)]

I can't get this working on natty with the "classic" desktop too, which is rather worrying.

[Jools Wills (jools)]

As this also affects the "classic desktop" should the bug be also assigned elsewhere, or a new bug opened for that (likely the same issue though)

[Jools Wills (jools)]

doing

killall mousetweaks; mousetweaks --ssc

makes the second click work for me, so perhaps mousetweaks is being started with the wrong options or something ? I'll try and debug it further.

[Jools Wills (jools)]

in maverick, in gconf-editor there is

/desktop/gnome/accessibility/mouse/

with delay_enable (bool) and delay_time (float)

these exist in natty too, but in natty delay_time is an int, and there is a "error" "This key has no schema". The key has no owner (in maverick it is mousetweaks).

missing some config stuff here? I'm not familiar with the functioning of the gnome configuration stuff, but ill keep digging if this bug doesnt get fixed first :)

[Jools Wills (jools)]

 ok. this looks like a mousetweaks bug. The new 3.0 version of mousetweaks seems to miss agconf schema that was in the older version. downgrading to the maverick version fixes this.

[Gerd Kohlberger (lowfi)]

There's a version mismatch between mousetweaks and gnome-control-center + gnome-settings-daemon. The GNOME 3 versions of these modules use dconf for configuration and the 2.32 versions use gconf. Downgrading mousetweaks to 2.32 will fix it. (or upgrading the others)

[Jeremy Bícha (jbicha)]

Not a Unity bug.

[Jeremy Bícha (jbicha)]

I don't believe this is an upstream bug either.

[Jeremy Bícha (jbicha)]

Ok, I triaged this bug and marked it as High importance, since it is a regression in accessibility that affects the entire desktop. Thank you for reporting this bug!

[Jools Wills (jools)]

thanks for reassigning/sorting the bug metadata. I was trying to assign it to "mousetweaks unity" but seemed unable to do so (probably because it was assigned already to unity (ubuntu) - no doubt user error ;-) . Pleased it has some attention now.

[Jools Wills (jools)]

I was asked on #ubuntu-dev to add a short "steps to reproduce" on here so. in case it is needed (although none of the mouse accessibility stuff works due to the configuration changes gconf to dconf as was mentioned by Gerd earlier, so it is quite easy to reproduce by trying either simulate second click or dwell click)

on Mousetweaks 2.32.x + gnome-control-center 2.32.x

1. Load gnome-mouse-properties
2. Choose Accessibility Tab
3. Turn on Simulated second click.
4. Hold down the left mouse button, and it "fills" and you get a right mouse click

on Mousetweaks 3.0.0 + gnome-control-center 2.32.x

1. Load gnome-mouse-properties
2. Choose Accessibility Tab
3. Turn on Simulated second click.
4. Hold down the left mouse button, and nothing happens.

Similar with dwell click.

[Francesco Fumanti (frafu)]

> Secondly, as a click and hold is already being utilised to move entries in the unity menu, how
> should this interact with this accessibility option. take for example a single click touchscreen.

The problem might be fixed by differenciating between a click and hold where the pointer does not move and a click and drag. I suppose nautilus does it that way as it is possible to perform a simulated secondary click on the items in a nautilus window.

[Jools Wills (jools)]

Any change of an update as to when this would be fixed? Doesn't feel like accessibility is any sort of priority for Ubuntu when an important issue like this (which is easy to fix), is left open for two months after release.

[Charlie Kravetz (cjkgeek)]

With 97,000 plus open bugs, importance sometimes depends on a developer actually being able to work an individual bug. This is a very important issue, however, that does not mean a developer has the opportunity to jump on it and fix it. There could be another, more important bug they are working.

[Jools Wills (jools)]

I'd be happy to help in any way I can.

My thinking to a quick fix is a fake version numbered mousetweaks 2.32 so something like 3.0.0+really2.32 or so, just until the next ubuntu release is out.

I understand there are lots of open bugs, but a lot is the fault of the way ubuntu is scheduled for release every 6 months. Had ubuntu the concept of "blocker bugs", major issues like this could get ironed out before release. I had to maintain my own mdadm package on my ppa, due to the ubuntu one not getting any attention previously, despite having posted fixes/patches and highlighted the issues. I still have unactioned patches on launchpad, so please also understand my frustrations too.

This bug is an easy fix in terms of time needed vs results, so I hope that it is looked at soon.

[Jools Wills (jools)]

still nothing ? Would you like me to build you an older mousetweaks package with a newer version number, and submit it? You have to take accessibility stuff like this more seriously, or else, there is no point writing up all the documents that state how good ubuntu is for this. this is an easy fix. I hope no-one who really needed this feature to operate their machine installed natty :/

[Jools Wills (jools)]

well, apart from me of course, and the others that use my modified distribution of Ubuntu for the O2 Joggler, but luckily I fixed it for them.

[Jools Wills (jools)]

Well, I have given up hope of having this fixed. At least I fixed it for my users of joggler ubuntu. it's a quick fix. this will no doubt remain "high priority" unless naty gets to end of life and then closed. shame :(

[Omer Akram (om26er)]

this won't be fixed in Natty I am afraid.

[Jools Wills (jools)]

Might as well close it, as it isn't an issue with later releases.

[dino99 (9d9)]

eol reached https://wiki.ubuntu.com/Releases