ion "PalmDetect""1"
Option "HorizEdgeScroll" "1" # does not work well with buttons
below
Option "MaxDoubleTapTime" "150"
Option "FingerLow" "24"
Option &quo
Package: x11-xserver-utils
Version: 7.6+3
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropiate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this a
rent 1024 x 600" above. As noted in the first report,
"current" changes to 1024 x 1024 despite --mode 1024x600. I am not
sure whether that is significant.
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
.
After the upgrades, and the same xrandr command, the panning seems
to be restricted to approximately 601 or 602 pixels.
This is surely a bug, or is the xrandr command not the correct way to
enable panning across a virtual screen? Is there some documentation
I have missed?
ael
--
To
On Sat, Oct 01, 2011 at 12:42:26PM +0200, Julien Cristau wrote:
> On Sat, Oct 1, 2011 at 10:47:54 +0100, ael wrote:
>
> > I now confirm that panning seems to be restricted to 1 or 2 pixels
> > (vertically in this case).
> >
> > To summarize, before the rece
I have now found that the problem that I encountered is more
subtle.
1) Only some of the synaptics functions were disabled. In particular,
the second right (button 3) was not recognised. However scrolling
was still working.
2) Restarting X re-enabled full button recognition. Maybe a race
so
My synaptics touchpad is not longer working because the module is
uloaded:
- extract from Xorg.log --
[40.390] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad
(/dev/input/event11)
[40.390] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evde
This problem with a partially disabled touchpad - the right button
failing to work is especially problematic - seems to have become
more severe. Restarting X repeatedly is now failing to clear the
problem.
I can see no obvious recent package upgrade that might explain the
problem. But many of the
The Synaptics right button disabled is present almost every time I start
X.
One new datum: if I
rmmod psmouse; modprobe psmouse
then on the controlling terminal (but not in /var/log/Xorg.log) I get
[typed by hand since copy-and-paste no longer possible]:
-
I now believe that the problem arose on the xserver-xorg upgrade to 1:7.6+9.
I will consider whether I should raise a new bug against xserver rather
than synaptics...
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@list
On Mon, Nov 28, 2011 at 03:00:54AM +0100, Cyril Brulebois wrote:
> ael (27/11/2011):
> > Attempting to start x as a normal user segfaults.
>
> You're getting VESA here.
>
> > Starting as root succeeds...
>
> And MGA there.
Yes, but I noted that the same
On Sat, Oct 22, 2011 at 05:59:54PM +0100, ael wrote:
> The Synaptics right button disabled is present almost every time I start
> X.
The problem is not with X: gpm and mev also fail to detect the
right button before X is started.
Nor does it seem to be a kernel problem: using an older
xserver-xorg-input-synaptics version 1.5.99.904-1 seems to have fixed
this, so I will close the bug.
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2012
Apologies :-( Last message sent to wrong bug. This is *not* fixed by
any synaptics update
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120501135
Package: xserver-xorg-input-synaptics
Version: 1.8.1-1
Severity: normal
You will see from below that I have an InputClass section for a
Synaptics touch pad. The odd thing is that while the
"EmulateMidButtonTime" setting is working (as revealed by synclient),
the other Options like "HorizEdgeScroll
Package: xserver-xorg-input-synaptics
Version: 1.8.1-1
Severity: normal
I first noticed this today (17/12/14) although it is possible that it
happened yesterday. Checking /var/log/dpkg.log, no obvious (to me)
package update stood out.
If I have several xterms open, and I work in one, then updati
Just realised that the same is happening in firefox. I noticed this
for the first time (I think) yesterday. Presumably certain xevents
are being missed? I couldn't figure out a way to use xev to
investigate this problem.
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
reloading the psmouse driver
fixes that. Not sure that that is connected: unlikely, I think.
Both report the trackpad as "Vendor 0x2, Product 0x7". I am not sure how
to get further information on the hardware differences, although I guess
they might both be using the same chip.
ael
--
To U
I spoke too soon. I am now seeing pointer freezes on the amd64 machine.
Different phenomena, but perhaps associated. I need to switch to a
pseudo terminal and "rmmod psmouse; modprobe psmouse" to get control
of the pointer back under X. gpm was still working in the pseudo
terminal before the reload
r Marble Mouse (ael)
ACTION!="add|change", GOTO="xorg_marble_end"
KERNEL!="event*", GOTO="xorg_marble_end"
#ENV{ID_PATH}!="platform-i8042-serio-1", GOTO="xorg_marble_end"
# Above for PS/2, misses USB. name below seems to be enough
ATTRS{
On Sat, Dec 28, 2013 at 08:32:32PM +0100, Julien Cristau wrote:
> On Fri, Dec 27, 2013 at 16:22:21 +0000, ael wrote:
>
> > Package: xserver-xorg-input-evdev
> > Version: 1:2.8.2-1
> > Severity: normal
> >
> > >From Xorg.0.log:
> >
> > (EE)
xorg.conf includes:-
Section "InputClass"
Identifier "marble_FX"
Driver "evdev"
MatchProduct"ImExPS/2 Logitech Explorer Mouse|Logitech USB
Trackball|PS2++ Logitech Mouse|PS2++ Logitech T
xserver-xorg-input-joystick-1:1.1.0-1 seems to be completely broken as
reported here: I hit the same bug on 2 completely different machines,
one i386 and the other amd64 architecture.
Upstream appear to have extensively patched and presumably fixed the
problem on 13/3/2007. Any chance of a new of
Package: xserver-xorg-input-mouse
Version: 1:1.4.0-4
Severity: important
Tags: patch
Most logitech trackballs do not work because there is no fdi file included.
Either such a file needs to be included in this package since trackballs
are perhaps variants of mice, or there needs to be an extra pack
er /etc/hal/fdi/policy/.
I think the package needs to install it somewhere like
/usr/share/hal/fdi/information/10freedesktop/
Thanks,
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Julien Cristau wrote:
On Sat, Nov 28, 2009 at 13:35:21 +, ael wrote:
Julien Cristau wrote:
You'll need to explain in more details what doesn't work, so that it can
be fixed properly instead of hacked around in an fdi file.
It is (default) button mapping. Of course, users m
Assigned Display Device: DFP-0
(II) Dec 26 12:39:45 NVIDIA(0): Validated modes:
(II) Dec 26 12:39:45 NVIDIA(0): "1680x1050"
(II) Dec 26 12:39:45 NVIDIA(0): Virtual screen size determined to be 1680 x 1050
(--) Dec 26 12:39:45 NVIDIA(0): DPI set to (90, 88); computed from "UseE
====
It looks as if the EDID block is being read correctly if I understand
http://en.wikipedia.org/wiki/Extended_display_identification_data .
At least the only difference looks like byte 20 which is presumably
just noting the difference between the VGA and DVI signals. But I have not
checked properly.
Why should the nv driver interpret the tiiming data differently for different
interfaces?
In passing, it seems that the closed source nvidia driver also has problems
with this monitor on DVI-D. Is Dell doing something evil in its monitors?
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
In my previous report I had only noticed a single byte difference in the EDID
dumps over
vga as opposed to DVI. In fact there are four:-
$ cmp -l edid.bin_vga edid.bin_DVI
11 33 34
21 16 200
100 24 21
128 113 333
My attempt to decode these didn't seem to match
http://en.wikipedia.org/w
rely can't a difficult problem to fix?
Clearly the nv driver has another issue with panel size.
As far as I can see, this part of the edid specification (as on Wikipedia) is
unambiguous so a fix ought to be simple?
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a
wever, it does look as if it is still a panel size problem with nv rather
than the
pixel clock.
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: xserver-xorg-input-joystick
Version: 1:1.4.1-1
Severity: grave
Justification: renders package unusable
Log file covers everything, I think:-
X.Org X Server 1.6.5
Release Date: 2009-10-11
X Protocol Version 11, Revision
the hal-fdi
configuration to udev? This seems to be a major usability bug.
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
-trackball.rules
Here are the contents:
-
# Logitech Marble Mice PN 804377-, PN 810-000767 or
# PN 804251- connected via USB or PS/2
# Marble FX or Marble Mouse (ael)
ACTION!="add|change", GOTO="xorg_mar
# PN 804251- connected via USB or PS/2
# Marble FX or Marble Mouse (ael)
ACTION!="add|change", GOTO="xorg_marble_end"
KERNEL!="event*", GOTO="xorg_marble_end"
#ENV{ID_PATH}!="platform-i8042-serio-1", GOTO="xorg_marble_end"
# Abov
On Sat, Mar 06, 2010 at 01:05:00PM +0100, Brice Goglin wrote:
> ael wrote:
> > I could send my rules if it would be useful.
> >
>
> Yes, please, it could help some people, especially the submitter.
In my quick reply, I hadn't noticed that this was a bug report.
e FX or Marble Mouse (ael)
ACTION!="add|change", GOTO="xorg_marble_end"
KERNEL!="event*", GOTO="xorg_marble_end"
#ENV{ID_PATH}!="platform-i8042-serio-1", GOTO="xorg_marble_end"
# Above for PS/2, misses USB. name below seems to be en
lls). Or should they appear as examples in one of the packages?
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100415141706.ga4...@conquest3.conquest
at
was the upstream release. I confirm that NoAccel appears to fix the
problem on 1:0.0.16+git20101210+8bb8231-2. Although the non accelerated
version is very painful compared to nv :-( .
Will test unstable version later today, I hope.
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@list
. boot with
Turning off acceleration fixes the problem as with the earlier
version.
I will report upstream when I have read about their tracking system
Thanks for the help,
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
Package: xserver-xorg-input-synaptics
Version: 1.4.0-1
Severity: important
After the recent testing upgrades, my Synaptics configuration specified
in my xorg.conf:-
--
Section "InputClass"
Identifier "SynPS/2 Synaptics TouchPad"
uired power cycle to reboot :-)
I am now trying to find where
InputClass "evdev touchpad catchall"
and
InputClass "touchpad catchall
are defined and whether these are the root cause of the problem.
ael
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject
On Fri, Apr 29, 2011 at 09:46:53PM +0200, Julien Cristau wrote:
> On Fri, Apr 29, 2011 at 20:03:38 +0100, ael wrote:
>
> > Package: xserver-xorg-input-synaptics
> > Version: 1.4.0-1
> > Severity: important
> >
> >
> > After the recent testing upgr
I have just discovered /usr/share/X11/xorg.conf.d/50-synaptics.conf
I hadn't seen any documenataion of these new configuration files :-(
Moving 50-synaptics.conf out of the way changes things: the touchpad
is now configured in some as yet unknown way. It is far too sensitive
and is almost unusabl
On Fri, Apr 29, 2011 at 10:06:55PM +0200, Julien Cristau wrote:
> On Fri, Apr 29, 2011 at 20:57:14 +0100, ael wrote:
>
> > I tried adding
> > Option "Device""/dev/input/event10"
> > into xorg.conf in the hope that it would ensure that t
On Fri, Apr 29, 2011 at 10:41:26PM +0200, Julien Cristau wrote:
> On Fri, Apr 29, 2011 at 21:36:25 +0100, ael wrote:
>
> > Ok. I saw the MatchIsTouchpad in 50-synaptics.conf and was about to
> > look at the man page. I guess these are new parameters since I
> > last read
uot;100"
Option "VertTwoFingerScroll" "true"
Option "HorizTwoFingerScroll" "true"
Option "MinSpeed" "0.5"
Option "MaxSpeed" "20"
Option "HorizEdgeScroll" &
47 matches
Mail list logo
