Julien Cristau jcris...@debian.org writes:
On Fri, Jul 27, 2012 at 02:39:14 +0100, Wookey wrote:
A way to confirm if the slowkeys feature is currently engaged would
allow me to confirm this more directly next time.
Vincent Lefevre vinc...@vinc17.net writes:
I've finally found the solution:
# apt-get install xkbset
$ xkbset -a
Thanks. That's useful. But I found an even better solution:
apt-cache search xdm
(install one of the alternatives)
apt-get purge gdm3
This has the extra bonus that
Vincent Lefevre vinc...@vinc17.net writes:
On 2012-07-20 08:58:57 +0200, Vincent Lefevre wrote:
So, it would seem that some part of the system would enable SlowKeys
in my back for one of the keyboards (I recall that when this happens
while I'm using the USB keyboard, only the USB keyboard is
may be pinned for either use by the scanout or through sharing
with another application, under those circumstances we cannot replace
the bo itself but must force the blit for PutImage.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=31367
Reported-and-tested-by: Bjørn Mork bj...@mork.no
problem
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Signed-off-by: Bjørn Mork bj...@mork.no
---
src/i830_uxa.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/src/i830_uxa.c b/src/i830_uxa.c
index 61e857f..c34ba18 100644
--- a/src
Julien Cristau jcris...@debian.org writes:
On Tue, Nov 2, 2010 at 15:09:49 +0100, Bjørn Mork wrote:
- first time the client window is switched to fullscreen the backlight dims
to a very
low setting. The backlight can be adjusted up again using ordinary
backlight controls
so
Cyril Brulebois k...@debian.org writes:
Christian Henz chrh...@gmx.de (03/11/2010):
I wrote a small test program that exposes this behaviour. One thing
to note is that the problem only occurs if the program in question
is running at the native screen resolution (1680x1050 in my case).
So
ow...@bugs.debian.org (Debian Bug Tracking System) writes:
Not a bug, the x11_options in udev is now ignored. Use xorg.conf to
set options, using an InputClass section with e.g. the MatchIsTouchpad
option (see the xorg.conf manpage and
whether this is a good idea or not, but it does at least restore
the previous behaviour for me. YMMV
Bjørn
pgp237BgTtL2m.pgp
Description: PGP signature
From: Bjørn Mork bj...@mork.no
Subject: Keep looking for x11_options in udev for now
Our drivers don't ship xorg.conf.d snippets for now, so
Bjørn Mork bj...@mork.no writes:
I see that I have the same issue of vesafb loaded befor the Intel fb. Is this
the problem? If so, then I guess either xserver-xorg-video-intel or the
kernel should prevent it. I've not done anything to force vesafb AFAIK
Well, not intentionally at least
Julien Cristau jcris...@debian.org writes:
On Fri, Jan 8, 2010 at 13:59:50 +0100, Bjørn Mork wrote:
Just did an upgrade:
2010-01-08 11:04:22 upgrade xserver-xorg-input-synaptics 1.2.0-2 1.2.1-1
and lost tapping in the process. The buttons still work, but I'm kind
of accustomed to use
Julien Cristau jcris...@debian.org writes:
I'd really prefer not to do that. Configuring stuff in hal or udev is
just a stopgap until X grows a way to handle hotplugged devices in
xorg.conf (which will happen with xserver 1.8), so I think we shouldn't
recommend/document this as the way to
Julien Cristau jcris...@debian.org writes:
On Mon, May 11, 2009 at 14:38:35 -0500, Adam Majer wrote:
David Nusinow wrote:
Please see http://wiki.debian.org/XStrikeForce/InputHotplugGuide for the
rationale and #515214 for more info.
That is great, yet it does nothing for me except change
13 matches
Mail list logo