I am also experiencing random keyboard failures similar to those reported. It
appears to me that they started for me after the latest X upgrade:
2008-01-04 13:24:54 upgrade xserver-xorg-input-kbd 1:1.2.0-1+1.2.1 1:1.2.2-3
The failure might happen randomly once a day. What happens is that the
Package: xserver-xorg-video-savage
Version: 1:2.0.2.3-1
Severity: grave
Justification: renders package unusable
There is nothing in this package. Probably a packaging mistake.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: x11-common
Version: 1:7.3+14
I took the example 40custom_load-xmodmap file from the man page verbatim and
it did not have any effect. My .Xmodmap file works if I call it with xmodmap
directly after being logged into an X session. The .Xmodmap file says:
keycode 160 = XF86AudioMute
ke
On Wednesday 30 July 2008 09:12:28 Julien Cristau wrote:
> On Tue, Jul 29, 2008 at 23:49:02 +0300, Peter Eisentraut wrote:
> > Is this example obsolete? Is there something else that might mess up the
> > keyboard configuration? Any clue? Thanks.
>
> Yes, that's a
Package: xfs
Version: 1:1.0.8-2.1
Severity: wishlist
Tags: patch
User: pet...@debian.org
Usertags: initd-status-support
Here is a patch to support the "status" action in the init.d script.
diff -u xfs-1.0.8/debian/xfs.init xfs-1.0.8/debian/xfs.init
--- xfs-1.0.8/debian/xfs.init
+++ xfs-1.0.8/debia
5 matches
Mail list logo
