That worked, thanks! I don't know if it is something you can do on the X11 end, but it would be very usefull if it could give a more informative error message.
Thanks -Thue On Tuesday 09 March 2004 15:31, Christian Guggenberger wrote: > On 09.03.2004 11:06 Thue Janus Kristensen wrote: > > Package: xfree86 > > Severity: normal > > Followup-For: Bug #236998 > > > > > > I see this problem too when displaying emacs windows from a > > debian woody (X version 4.1.0-16woody3) on my unstable > > system (4.3.0-5). I have a nvidia gfx card, using the xfree > > open source driver. > > > > I can 100% reproducibly produce a crash with the following > > steps: -Start emacs from woody box, displayed on unstable > > box -In scratch buffer, set a mark (CTRL-space) in top left > > corner. -Go to buttom right corner and push (META-w). > > -Emacs crashes with the following error: > > > > [EMAIL PROTECTED]:~$ X protocol error: BadWindow (invalid Window > > parameter) on protocol request 25 > > > > [2]+ Exit 70 emacs > > > > That is not the only way it crashes, it is generelly hard to > > keep it working for 5 minuttes. It would be nice if this was > > fixed :). > > what do you mean by 'Start emacs from woody box, displayed on > unstable box' ? > > do you log into the woody box with ssh? > When you using ssh-3.8p1, lease try the following: > > (quoted from Bug#236936, Colin Watson) > Starting with 3.8, you need to set ForwardX11Trusted if you > want to affect other X clients. From ssh_config(5): > > ForwardX11Trusted > If the this option is set to ``yes'' then remote > X11 clients will have full access to the original X11 dis- > play. If this option is set to ``no'' then remote X11 clients > will be considered untrusted and prevented from stealing or > tampering with data belonging to trusted X11 clients. > > The default is ``no''. > /quote > > hth. > Christian
