debian/changelog | 12 +---
debian/libegl1-mesa-dev.install.linux.in |2 +-
2 files changed, 10 insertions(+), 4 deletions(-)
New commits:
commit af071f7eb2cce284cbd65e64c4f81bdd00e0c260
Author: Christopher James Halse Rogers
Date: Fri Feb 24 13:43:33 2012
Hi,
I'm playing with an old ThinkPad A22p, which contains a Rage128 chip.
After upgrading to squeeze, it gave me the same "black screen" and
infinitely-repeating "Idle timed out, resetting engine" message in
Xorg.0.log.
Installing firmware seems to have helped. However, this doesn't
entirely solv
> Oh, I'm not saying it's possible today, I'm saying it's where it should
> be happening (it knows when a device gets plugged in, it has some
> knowledge of input device configuration, so making that per-device
> should be possible). If gsd isn't suitable, it shouldn't be too hard to
> write a pro
> /etc/init.d/x11-common on boot should run before any unprivileged user
> has a chance to do anything (it's in rcS.d, and depends only on
> $local_fs), so it's less of a problem than initial package installation
> AFAICT.
I'm not that familiar with the newer dependency boot sequencing, but I
know
On Thu, Mar 1, 2012 at 14:31:35 -0500, Stefan Monnier wrote:
> >> Where are the equivalent of xorg.conf's MatchIsKeyboard/MatchProduct/...?
> > gnome-settings-daemon.
>
> Can you point me to some documentation as to how I'd use
> gnome-settings-daemon to setup a particular XKB config on all curr
On Thu, Mar 1, 2012 at 12:39:41 -0800, Tim wrote:
> I think there is still a race in your version in the lines which look
> like:
>
> > + mkdir $ICE_DIR 2>/dev/null || [ -d $ICE_DIR ] && ! [ -h $ICE_DIR ]
>
> mkdir will fail if the file already exists for any reason. After
> mkdir fails, it i
>> Where are the equivalent of xorg.conf's MatchIsKeyboard/MatchProduct/...?
> gnome-settings-daemon.
Can you point me to some documentation as to how I'd use
gnome-settings-daemon to setup a particular XKB config on all current
and future keyboards?
(maybe a relevant detail of that XKB config: it
Hi Julien,
> > As far as the short-term solution to this problem goes, how about
> > this (untested)?
> >
> >
> > if [ -e $SOCKET_DIR ] && [ ! -d $SOCKET_DIR ]; then
> > mv $SOCKET_DIR $SOCKET_DIR.$$ || exit $?
> > fi
> > if [ ! -e $SOCKET_DIR ]; then
> > mkdir $SOCKET_DIR || exit $?
On Thu, Mar 1, 2012 at 11:55:29 -0800, Tim wrote:
> As far as the short-term solution to this problem goes, how about
> this (untested)?
>
>
> if [ -e $SOCKET_DIR ] && [ ! -d $SOCKET_DIR ]; then
> mv $SOCKET_DIR $SOCKET_DIR.$$ || exit $?
> fi
> if [ ! -e $SOCKET_DIR ]; then
> mkdir $SOC
As far as the short-term solution to this problem goes, how about
this (untested)?
if [ -e $SOCKET_DIR ] && [ ! -d $SOCKET_DIR ]; then
mv $SOCKET_DIR $SOCKET_DIR.$$ || exit $?
fi
if [ ! -e $SOCKET_DIR ]; then
mkdir $SOCKET_DIR || exit $?
chown root:root $SOCKET_DIR
chmod 1777 $SOC
On Wed, Feb 29, 2012 at 20:25:14 -0500, Stefan Monnier wrote:
> Where are the equivalent of xorg.conf's MatchIsKeyboard/MatchProduct/...?
gnome-settings-daemon.
Cheers,
Julien
signature.asc
Description: Digital signature
On Tue, Feb 28, 2012 at 08:37:59PM +0100, Julien Cristau wrote:
> On Tue, Feb 28, 2012 at 12:52:12 -0500, Jeffrey Sheinberg wrote:
>
> > The result - started up emacs, instant crash in the x-server.
> >
> > Attached is the xorg log file from just after the above
> > crash - it was actually named
>> It seems that setxkbmap only affects the current InputDevice, whereas
>> I'd like to affect a whole InputClass, but I don't know how/where
>> to specify which inputs devices should be affected.
>> Where are the equivalent of xorg.conf's MatchIsKeyboard/MatchProduct/...?
>> Tho to tell you the tr
13 matches
Mail list logo
