After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 446789 - _NET_MOVERESIZE_WINDOW support fails
_NET_MOVERESIZE_WINDOW support fails
Status: RESOLVED DUPLICATE of bug 448183
Product: metacity
Classification: Other
Component: general
trunk
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2007-06-12 16:17 UTC by Lluís
Modified: 2008-02-21 02:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Lluís 2007-06-12 16:17:59 UTC
Please describe the problem:
I've tried to use the functionality added by Bug #344521, by compiling from svn metacity and wnck, but wmctrl is unable to move windows to the desired place (although it can resize them), as well as the testcase program attached in the aforementioned bug. In fact the resize is also not working as expected in the testcase program:

  Current geometry: 277,91 724x386
  Current geometry: 277,91 715x401
  Current geometry: 277,91 706x416
  Current geometry: 277,91 697x431
  Current geometry: 277,91 688x446

I've also tried to use that functionality through python-wnck (recompiling from svn both pygtk and gnome-python-desktop), but it is unable to resize nor move the windows.

I'm using gnome 2.18 (debian testing+sid, except for the aforementioned recompiled packages from gnome's svn) on an amd64-like box.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Lluís 2007-06-12 16:20:09 UTC
See following attachments for both my testing scripts (attached in Bug #344521):
  Attachment #89809 [details]
  Attachment #89810 [details]
Comment 2 Thomas Thurman 2008-02-20 03:31:49 UTC
This is a dupe of bug 448183, isn't it?
Comment 3 Thomas Thurman 2008-02-21 02:08:11 UTC
Assuming it is for now.

*** This bug has been marked as a duplicate of 448183 ***