Bug 7556 - all X11 output frozen while moving/resizing windows
all X11 output frozen while moving/resizing windows
Product: Red Hat Linux
Classification: Retired
Component: enlightenment (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
Depends On:
  Show dependency treegraph
Reported: 1999-12-03 11:42 EST by David Balažic
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-17 15:57:32 EST
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 David Balažic 1999-12-03 11:42:07 EST
While moving or rezising windows ( not opaque mode , but only with frame
outline ) all gfx output is frozen, like on AmigaOS :-)
I think this even causes xmms to stop playing , because it tries to update
the time-position. Happens with other windowmanagers too.
( But not on IRIX 5.3 , so I don't see why it must block on linux )
Comment 1 Elliot Lee 2000-01-17 15:57:59 EST
Cannot reproduce. It is possible that on a very slow system, moving the window
around would use up all the CPU time.
Comment 2 David Balažic 2000-01-18 09:06:59 EST
The enlightenment window manager ( and some others too , like the CDE WM )
blocks all gfx while the outline of the window is visible, while moving or
resizing it. Note that the moving-mode is outline/boxed/... so that only the
a single box is dragged and the window appears at the new position when the
mouse button is released ( as opposed to opaque moving , when the window is
moved/resized in real-time as the mouse is moved ). Whether this is a bug or
just a compromise between speed and functionality is a matter of opinion.
The 4Dwm ( from IRIX ) does not block gfx , tested with the same X server, but
the outline flickers, they must have some special support in the SGI X server.

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