Debian Bug report logs - #11174
fvwm2: crash fvwmbuttons by changing xterm title

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joey@kite.ml.org>

To: submit@bugs.debian.org

Subject: fvwm2: crash fvwmbuttons by changing xterm title

Date: 11 Jul 1997 19:00:27 -0000

Package: fvwm2
Version: 2.0.45-BETA-4

This is a weird one..

I have my prompt set up so it displays my pwd and some other info on the
title bar of my xterm. I notice that if I put an xterm right below my
fvwmbuttons window, make the xterm rather large (80x43 characters), and
press and hold down enter (which makes my prompt be displayed many times,
rapidly, and so results in the xterm title being updated constantly), while 
moving my mouse cursor off of the xterm and onto fvwmbuttons, then 
fvwmbuttons crashes and disappears. Here are the error messages I get in 
xsession-errors when I do this:

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  4 (X_DestroyWindow)
  Resource id in failed request:  0x2c0000f
  Serial number of failed request:  440
  Current serial number in output stream:  443
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  62 (X_CopyArea)
  Resource id in failed request:  0x6800022
  Serial number of failed request:  801
  Current serial number in output stream:  817
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  4 (X_DestroyWindow)
  Resource id in failed request:  0x1c0000d
  Serial number of failed request:  1268
  Current serial number in output stream:  1273

My hypothesis it that fvwmbuttons doesn't like the title of a window to
change when fvwmbuttons is becoming active, and my setup is just making this
bug easy to reproduce.

I'll providemy fvwmrc on request, the only relevant thing I can think of is
that I have sloppyfocus and focus-follows-mouse turned on.

-- System Information
Debian Release: 1.3
Kernel Version: Linux kite 2.0.30 #13 Wed May 28 23:49:18 EDT 1997 i586 unknown

Versions of the packages fvwm2 depends on:
libc5	Version: 5.4.23-4
xlib6	Version: 3.3-3
xpm4.7	Version: 3.4g-9

Message #10 received at 11174@bugs.debian.org (full text, mbox, reply):

From: Austin Donnelly <austin@greenend.org.uk>

To: Joey Hess <joey@kite.ml.org>, 11174@bugs.debian.org

Subject: Re: Bug#11174: fvwm2: crash fvwmbuttons by changing xterm title

Date: Mon, 14 Jul 1997 22:00:16 +0100 (BST)

On , 11 Jul 1997, Joey Hess wrote:

> I have my prompt set up so it displays my pwd and some other info on the
> title bar of my xterm. I notice that if I put an xterm right below my
> fvwmbuttons window, make the xterm rather large (80x43 characters), and
> press and hold down enter (which makes my prompt be displayed many times,
> rapidly, and so results in the xterm title being updated constantly), while 
> moving my mouse cursor off of the xterm and onto fvwmbuttons, then 
> fvwmbuttons crashes and disappears. Here are the error messages I get in 
> xsession-errors when I do this:
> 
> X Error of failed request:  BadWindow (invalid Window parameter)
>   Major opcode of failed request:  4 (X_DestroyWindow)
>   Resource id in failed request:  0x2c0000f
>   Serial number of failed request:  440
>   Current serial number in output stream:  443
> X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
>   Major opcode of failed request:  62 (X_CopyArea)
>   Resource id in failed request:  0x6800022
>   Serial number of failed request:  801
>   Current serial number in output stream:  817
> X Error of failed request:  BadWindow (invalid Window parameter)
>   Major opcode of failed request:  4 (X_DestroyWindow)
>   Resource id in failed request:  0x1c0000d
>   Serial number of failed request:  1268
>   Current serial number in output stream:  1273
> 
> My hypothesis it that fvwmbuttons doesn't like the title of a window to
> change when fvwmbuttons is becoming active, and my setup is just making this
> bug easy to reproduce.
> 
> I'll providemy fvwmrc on request, the only relevant thing I can think of is
> that I have sloppyfocus and focus-follows-mouse turned on.

I can't seem to reproduce this: could you send me your fvwmrc,
including the FvwmButtons configuration, and the relevant part of your
startup scripts which set your prompt.

Thanks,
Austin

Message #15 received at 11174@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joey@kite.ml.org>

To: Austin Donnelly <austin@greenend.org.uk>

Cc: Joey Hess <joey@kite.ml.org>, 11174@bugs.debian.org

Subject: Re: Bug#11174: fvwm2: crash fvwmbuttons by changing xterm title

Date: Mon, 14 Jul 1997 17:28:04 -0400

[Message part 1 (text/plain, inline)]

Austin Donnelly wrote:
> I can't seem to reproduce this: could you send me your fvwmrc,
> including the FvwmButtons configuration, and the relevant part of your
> startup scripts which set your prompt.

I use zsh, and here's how I set my prompt:

# Select a prompt, which also shows up in the title of xterms.
baseprompt="%n@%m:%~"
if [ "${TERM}" = "xterm" -o "${TERM}" = "color_xterm" ]; then
        PROMPT=`echo -n -e "%{\033]0;$baseprompt\007%}$baseprompt>"`
else
        PROMPT="$baseprompt>"
fi
unset baseprompt

The xterm that this problem manifests in is, as I mentioned, a big xterm
window. To get one just like it, use "xterm -geom 80x43+494+75 -ls"

My fvwm configuration is probably the strangest one on earth. My fvwmrc is
generated by a perl program, and automatically resizes itself to the current
desktop size and adapts to different display types. I've attached the output 
of the program, for the display I experience this problem on.

-- 
see shy jo

[fvwmrc-out (text/plain, attachment)]

Message #20 received at 11174@bugs.debian.org (full text, mbox, reply):

From: Herbert Xu <herbert@greathan.apana.org.au>

To: Joey Hess <joey@kite.ml.org>, 11174@bugs.debian.org

Subject: Re: Bug#11174: fvwm2: crash fvwmbuttons by changing xterm title

Date: Sat, 19 Jul 1997 17:41:14 +1000

I've seen this too.  But what crashed in my case was FvwmPager.
-- 
Debian GNU/Linux 1.3 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://greathan.apana.org.au/~herbert/
PGP Key: http://greathan.apana.org.au/~herbert/pubkey.txt

Message #25 received at 11174@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joey@kite.ml.org>

To: Herbert Xu <herbert@greathan.apana.org.au>

Cc: Joey Hess <joey@kite.ml.org>, 11174@bugs.debian.org

Subject: Re: Bug#11174: fvwm2: crash fvwmbuttons by changing xterm title

Date: Sat, 19 Jul 1997 12:00:59 -0400

Herbert Xu wrote:
> I've seen this too.  But what crashed in my case was FvwmPager.

I have a pager swallowed in my button bar. Might be a connection there. But
I don't have to move the pointer over the pager..

-- 
see shy jo

Message #32 received at 11174@bugs.debian.org (full text, mbox, reply):

From: Julian Gilbey <J.D.Gilbey@qmw.ac.uk>

To: 11174@bugs.debian.org, 11174-submitter@bugs.debian.org

Subject: Bug#11174: fvwm2: crash fvwmbuttons by changing xterm title

Date: Mon, 19 Apr 1999 20:31:40 +0100 (BST)

This one looks very strange, as you said.  Before I try to reproduce
it, would it be at all possible for you to see whether the problem
still occurs with the stable release of FVWM (fvwm 2.2-x in potato)?

Thanks,

   Julian

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
             Debian GNU/Linux Developer.  jdg@debian.org
       -*- Finger jdg@master.debian.org for my PGP public key. -*-

Message #44 received at 11174-done@bugs.debian.org (full text, mbox, reply):

From: Alexander Kotelnikov <sacha@nwgsm.ru>

To: Debian BTS <11174-done@bugs.debian.org>

Subject: fvwm2: crash fvwmbuttons by changing xterm title

Date: Sat, 05 Jan 2002 20:18:55 +0300

I am very sure there is no such bug now. I could not reproduce it and
a bug similar to this disappeared some time ago also (FvwmPager
creashed when mouse cursor was on it and a new window image appeared
under the cursor)
-- 
Alexander Kotelnikov
Saint-Petersburg, Russia

Send a report that this bug log contains spam.