Date: Mon, 22 Oct 2007 17:09:20 +0400 From: Andrew Pantyukhin <infofarmer@FreeBSD.org> To: Chris Hill <chris@monochrome.org> Cc: FreeBSD Questions List <questions@freebsd.org> Subject: Re: Xmodmap (or .xinitrc?) broken after xorg upgrade Message-ID: <20071022130919.GK19997@amilo.cenkes.org> In-Reply-To: <20071021172841.H792@tripel.monochrome.org> References: <20071021172841.H792@tripel.monochrome.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 21, 2007 at 08:38:33PM -0400, Chris Hill wrote: > About a week ago, I updated my ports, including xorg. Now xmodmap isn't > running from ~/.xinitrc like it used to. > > My .xinitrc is the same as it's been for years, so it includes the lines > if [ -f $usermodmap ]; then > xmodmap $usermodmap > fi > > After some experimenting, I find that if I run > $ xmodmap .Xmodmap > $ xmodmap .Xmodmap > ...twice, as shown, in an xterm after X gets going - then my .Xmodmap takes > effect. > > If I comment out that section of ~/.xinitrc, then I only have to run > $ xmodmap .Xmodmap > once in an xterm. I would like not to have to run xmodmap manually at all, > but have .xinitrc take care of it, just as it used to be before the > upgrade. > > Any ideas? Many thanks in advance. No ideas, but a "same here". It's a good thing that I don't have to reboot all that often. Doesn't bother me enough to look deeper.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071022130919.GK19997>