Date: Sun, 11 Oct 2009 21:54:09 +0200 From: =?ISO-8859-1?Q?Marius_N=FCnnerich?= <marius@nuenneri.ch> To: David Wolfskill <david@catwhisker.org> Cc: ports@freebsd.org Subject: Re: xlockmore-5.29: "BadWindow (invalid Window parameter)" using virtual wm Message-ID: <b649e5e0910111254o13b45ec4q1a555f7a339d3baf@mail.gmail.com> In-Reply-To: <20091011185439.GQ1340@albert.catwhisker.org> References: <20091011185439.GQ1340@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi David, On Sun, Oct 11, 2009 at 20:54, David Wolfskill <david@catwhisker.org> wrote= : > This is running FreeBSD 6.4-STABLE r197725; I'm in the habit of > updating installed ports on my laptop daily (after updating the > stable/6 slice). > > The xlockmore port is at 5.29, updating 01 Oct 2009. > > I normally use the piewm Window Manager (I got used to tvtwm back in > '93, and piewm is based on it and is very similar). > > If I try to issue "xlock -mode random" using either piewm or tvtwm, I > now get: > > X Error of failed request: =A0BadWindow (invalid Window parameter) > =A0Major opcode of failed request: =A03 (X_GetWindowAttributes) > =A0Resource id in failed request: =A00x45 > =A0Serial number of failed request: =A082 > =A0Current serial number in output stream: =A083 > > If I exit either of those Window Managers and fire up twm, xlock does > not issue that message, and seems to run normally (at least in most > modes). > > I believe that this change in behavior coincided with the update to > xlockmore (01 Oct); I didn't mention it earlier because something odd > also appears to have happened with DRI support recently, and I wasn't > clear enough on the interrelationships to be reasonably confident that I > was reporting things properly. > > I also run stable/7 and head slices (each with the misc/compat6x port > installed, so I'm using a shared /usr/local among all slices). > xlockmore appears to run OK in 7.2-STABLE r197901 and head r197928, > though I'm unable to run X with DRI enabled in those environments. > > In checking the Net for other reports of similarissues, I see that > xlockmore has had issues in the past with virtual window managers (ref. > <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D309760>, from Thu, 19 > May 2005 11:18:03 UTC). > > Would it make more sense (for getting the issue resolved) for me to try > reverting xlockmore to the previous version or some other approach? > While I'm OK hacking code, I certainly don't claim much in-depth > understanding of much X-related code; on the other hand, I do have local > mirrors of the FreeBSD CVS & SVN repositories handy. > > Thanks! > > Peace, > david > -- > David H. Wolfskill =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0david@catwhisker.org > Depriving a girl or boy of an opportunity for education is evil. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. > Could you please write to David A. Bagley <bagleyd@tux.org> and explain this problem to him? He is the current maintainer of xlockmore.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b649e5e0910111254o13b45ec4q1a555f7a339d3baf>