Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Nov 2005 23:43:34 -0500
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        hartzell@alerce.com
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: Gnome, Xemacs, and BadWindow's.
Message-ID:  <1133325814.58509.16.camel@shumai.marcuscom.com>
In-Reply-To: <17292.64754.774767.955262@satchel.alerce.com>
References:  <17292.64754.774767.955262@satchel.alerce.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-3PGQA1AojA4UcJw6psb1
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2005-11-29 at 17:14 -0800, George Hartzell wrote:
> I'm moving my IBM T42p from 5.3BETA4 to 6.0 STABLE
>=20
> I've built all the xorg, gnome2, and xemacs stuff from ports
> portsnap'ed a couple of days ago w/ BATCH=3D1.
>=20
> I'm running a GENERIC kernel that was build from today's STABLE
> sources.
>=20
> I've created a new user w/ the default .files, using tcsh, and no
> emacs/xemacs configuration files, so it's unlikely to be anything in
> my personal configuration (?).
>=20
> The X server is running w/out any configuration file.
>=20
> Whenever I type a bit of text into xemacs and "kill" it (e.g. move to
> the beginning of the line hit control-k), I get a pair of messages in
> the xterm window from which I started xemacs:
>=20
>   X Error of failed request:  BadWindow (invalid Window parameter)
>     Major opcode of failed request:  18 (X_ChangeProperty)
>     Resource id in failed request:  0xe006b8
>     Serial number of failed request:  20223
>     Current serial number in output stream:  20225
>   X Error of failed request:  BadWindow (invalid Window parameter)
>     Major opcode of failed request:  25 (X_SendEvent)
>     Resource id in failed request:  0xe006b8
>     Serial number of failed request:  20224
>     Current serial number in output stream:  20225
>=20
> It only happens when nautilus is running.
>=20
> xlsclient -la tells me that nautilus has a window who's id is close
> to the resource id of the failed requests, but I don't know how those
> id's are generated:
>=20
>   Window 0xe00001:
>     Machine:  satchel.alerce.com
>     Name:  File Manager
>     Icon Name:  File Manager
>     Command:  nautilus
>     Instance/Class:  nautilus/Nautilus
>=20
> 'Sometimes' (I can't consistently repeat it), stopping nautilus,
> cutting something in xemacs, then starting nautilus will generate the
> pair of messages.
>=20
> I tried to get some feedback a while back about a similar problem that
> also involved ssh, here's a pointer to the start of that thread:
>=20
>   http://lists.freebsd.org/pipermail/freebsd-gnome/2005-June/011636.html
>=20
> I never really resolved it then, just stopped running nautilus (sadly
> it seems to be responsible for setting the background...).
>=20
> I get occasional mail from folks who see my earlier post, so I don't
> think I'm the only person seeing this.
>=20
> Anyone have any thoughts?
>=20
> I'd appreciate any leads, hints, pointers, me-too's, works-for-me's,
> etc....=20

I seem to recall seeing a lot of me-toos on the mailing list, but no one
has come up with a solution.  My solution is just to use vim :-D.  But
if this is important to you, you should float it in GNOME's Bugzilla.  I
don't see how this could be a FreeBSD-only problem.

Joe

--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-3PGQA1AojA4UcJw6psb1
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQBDjS32b2iPiv4Uz4cRAn85AKCZJevRa6JbHJL7XVLTm5J88hMAMgCfdgqm
KMH8rjXlaL7351tF2DCzYrI=
=G5a5
-----END PGP SIGNATURE-----

--=-3PGQA1AojA4UcJw6psb1--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1133325814.58509.16.camel>