From: Greg Wooledge <greg@wooledge.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: moving a window makes the system 'hang' until button is released
Date: Sun, 7 Sep 2003 09:17:14 -0400 [thread overview]
Message-ID: <20030907131714.GB11333@pegasus.wooledge.org> (raw)
In-Reply-To: <3F5ACA93.6020302@cyberone.com.au>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
Nick Piggin (piggin@cyberone.com.au) wrote:
> Hi Greg,
> Can you give my scheduler a try if you have time?
After discussion with Paul Cassella and some more experimentation
on my side, I've concluded that this is not a Linux kernel issue
at all -- it's a "feature" of fvwm. Specifically, fvwm grabs the
entire X server when it's doing a non-opaque move, and xmms only
keeps playing music until its buffer is drained. The xmms buffer
size seems to be dramatically smaller under ALSA, which is why I
never saw the problem until I moved to 2.6.0-test4 and ALSA.
I've changed "OpaqueMoveSize" in my .fvwm2rc file to 90, so it will
only use outline-mode for moving windows which are 90% of the size
of the screen -- i.e. never, for me. (Another workaround might be
to increase xmms's buffer size, but I haven't pursued that side yet.)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98091 is also
relevant here.
--
Greg Wooledge | "Truth belongs to everybody."
greg@wooledge.org | - The Red Hot Chili Peppers
http://wooledge.org/~greg/ |
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
prev parent reply other threads:[~2003-09-07 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 20:53 moving a window makes the system 'hang' until button is released Greg Wooledge
2003-09-07 6:05 ` Nick Piggin
2003-09-07 13:17 ` Greg Wooledge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030907131714.GB11333@pegasus.wooledge.org \
--to=greg@wooledge.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).