Bug 157395 - status window position not updated when using alt+tab
status window position not updated when using alt+tab
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: im-sdk (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jens Petersen
: i18n
Depends On: 139809
Blocks: IIIMF
  Show dependency treegraph
Reported: 2005-05-11 02:32 EDT by Lawrence Lim
Modified: 2014-03-25 20:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-29 23:14:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lawrence Lim 2005-05-11 02:32:51 EDT
+++ This bug was initially created as a clone of Bug #139809 +++

Description of problem:
Tested in the GNOME desktop envrionment, when the user move an application
around the desktop with LE activated, using alt+tab to switch to another
application and back to the original application of the LE activated, you will
notice that the status window is still at the old position where the application
used to be.

Please see attached screenshot. I dont think this is LE specific.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.in gdm, log in as normal user with any CJK locale
2.start g-t
3.in g-t, gedit &
4.in gedit, ctrl-space to activate LE
5.move gedit using mouse to another corner of the screen
6.alt-tab to switch back to g-t
7.alt-tab to switch back to gedit
Actual results:
status window is at the previous position of gedit application

Expected results:
the position should be updated

Additional info:
Comment 1 Lawrence Lim 2005-05-11 02:34:30 EDT
Bug still exist in U1, checked with iiimf-12.1-13.EL.
Comment 3 Jens Petersen 2005-09-29 23:14:48 EDT
AFAIK this still not fixed in current iiimf.
Closing out for now.

Note You need to log in before you can comment on or make changes to this bug.