[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#341536: marked as done (xnest does not propagate window manager events)

Your message dated Sun, 18 Feb 2007 12:15:12 +0100
with message-id <45D83540.30700@ens-lyon.org>
and subject line Bug#341536: xnest does not propagate window manager events
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xnest
Version: 6.8.2.dfsg.1-11

(My environment: sid/unstable
xserver-xorg: 6.8.2.dfsg.1-10
kdelibs: 4:3.4.3-2
)

When I start a window manager inside Xnest, changes to windows 
(raise/iconify/deiconify/resize) are not properly propagated (if at all).
The window itself behaves as if the event was handled through.

Steps to reproduce the problem: I used icewm inside a kde session. I had 
similar behaviour with "inner" window managers kde or twm, and without an 
"outer" window manager (plain X)

Steps to start a the window manager (as display ":3"):

  xterm #1:
  > xauth add $HOSTNAME/unix:3 . $(mcookie)
  > Xnest :3 -geometry 800x600

  xterm #2:
  > export DISPLAY=:3
  > icewm

Inside icmwm:

* Open two xterms
* Make them overlapping.

* Right-click title bar of lower window.
  Choose "raise"
=> The window dows not raise.

* Drag the window
=> NOW it raises.

OR:

* open an xterm
* resize the xterm
=> enlarged window is being clipped
=> border handles appear as if the window wasn't clipped
=> iconify/deiconfy cycle updates to correct size.

Mit freundlichem Gruß / With kind regards
	Holger Klawitter
--
info@klawitter.de

--- End Message ---
--- Begin Message --- 
All the steps that the submitter provided to reproduce the bug did not
show any problem with latest Xnest from Etch (2:1.1.1-17). Closing.

Brice

--- End Message ---
Reply to: