wmii thinks that closed xterms are unresponsive

hatliff / wmii

Automatically exported from code.google.com/p/wmii

MIT License

0 stars 0 forks source link

wmii thinks that closed xterms are unresponsive #186

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. open an xterm
2. close it with Mod-Shift-c
3.

What is the expected result? What do you see instead?
I expect the xterm to just close, which happens. But additionally, I get
the xmessage window telling me that the client is unresponsive.

What version of the product are you using (wmii -v)? On what operating
system (uname -a)?
wmii-hg2691, Python wmiirc

Please provide any additional information below.

Original issue reported on code.google.com by skwi...@googlemail.com on 3 Jun 2010 at 8:53

GoogleCodeExporter commented 9 years ago

This issue was closed by revision c26d9fd20d.

Original comment by maglion...@gmail.com on 3 Jun 2010 at 2:57

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Running changeset 2700 c8cd91c26eeb and this still persists. Not for all windows
-e.g. xterm is fine- but on most others.

Original comment by google@nemesis13.de on 4 Jun 2010 at 6:44

GoogleCodeExporter commented 9 years ago

Heh. I just got the title of another window in xmessage. Closed an urxvt 
terminal
which was in float mode and the xmessage reported the title of the underlying 
firefox
window (which is in stacked mode)

Original comment by google@nemesis13.de on 4 Jun 2010 at 7:27

GoogleCodeExporter commented 9 years ago

As I've said, your bug is different. This is fixed.

Original comment by maglion...@gmail.com on 4 Jun 2010 at 8:03