There must have been a misunderstanding here. I’m not going to support
my patches on GNOME 3. In fact, they are not needed there, as there is
the hook framework.
When time allows, I will update my PPA for Natty, but only because Natty
was released with GNOME 2. (And I understand them — GNOME 3 is
In GNOME, they decided that it is more appropriate to provide a hook
that will run a user-customizable script when an input device is added
or removed. The xinput or synclient invocations shown above can be added
to this hook. So, for all intents and purposes, this bug can be
considered “Fix
I’m afraid not, as whenever I happen to have enough free time to work on
this patch, both GNOME and Ubuntu turn out to be in feature freeze, and
extended configurability counts as a feature.
However, I will produce PPA builds for Maverick as soon as I get around
to installing the alpha and will
bornagainpenguin wrote:
No dice. The current package from Ubuntu is newer than the one in the PPA
I try to keep up and update my packages when a new version is released.
(Is there a way to receive an email notification when a new version of a
certain package is released?)
Uploaded an update;
I have added another patch that adds gconf settings for corner taps.
Available in my PPA for Lucid only.
As for changing defaults, I don’t really have a strong opinion. When
there is configuration options, who needs defaults? :)
--
Action for middle and right click is reversed since jaunty
Alex Dicks wrote on 2010-03-16:
Perhaps the defaults for those keys could be changed to give the Jaunty
behaviour back?
And then users who started using Ubuntu during the Karmic era will file
a bug that Lucid changed the defaults and broke their habits, just as we
are blaming Karmic here.
Added Karmic test packages to PPA.
--
Action for middle and right click is reversed since jaunty
https://bugs.launchpad.net/bugs/432814
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
Action for middle and right click is reversed since jaunty
https://bugs.launchpad.net/bugs/432814
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Updated patch.
** Patch added: 0001-Add-tap-to-click-button-settings.v8.patch
http://launchpadlibrarian.net/39888553/0001-Add-tap-to-click-button-settings.v8.patch
--
Action for middle and right click is reversed since jaunty
https://bugs.launchpad.net/bugs/432814
You received this bug
Test packages for Lucid are available in my ppa at
https://launchpad.net/~yurivkhan/+archive/ppa .
--
Action for middle and right click is reversed since jaunty
https://bugs.launchpad.net/bugs/432814
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
OK, here’s a status update.
The patch I sent upstream has passed peer review, but GNOME is currently
in feature freeze in preparation for 2.30 release. I have filed for a
freeze break, but only received one “not totally against” reply so far,
so I’m not confident a break will be granted.
So I’d
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=598820
Importance: Unknown
Status: Unknown
--
Action for middle and right click is reversed since jaunty
https://bugs.launchpad.net/bugs/432814
You received this bug notification because you are a
OK, I looked a little further, here’s my understanding.
* The touchpad is first configured with xorg.conf, hal policies and the code in
xserver-xorg-input-synaptics.
* When GNOME starts, the gnome-settings-daemon kicks in. It has a mouse plugin
that resets TapButton# settings every once in a
I had the impression that TapButton# options could be configured in the
appropriate InputDevice section of xorg.conf, but right now I seem to be
unable to do so. The Xorg.0.log reports no errors but synclient -l lists
TapButton2=3 and TapButton3=2.
--
Action for middle and right click is
14 matches
Mail list logo
