public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit@transpect.com>
To: Tim Moore <timothymoore@bigfoot.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.19 Realaudio masq problem
Date: Wed, 25 Apr 2001 13:38:04 -0500	[thread overview]
Message-ID: <20010425133804.A1094@free.transpect.com> (raw)
In-Reply-To: <20010424201403.A1909@free.transpect.com> <3AE621D1.FE45602B@bigfoot.com>
In-Reply-To: <3AE621D1.FE45602B@bigfoot.com>; from timothymoore@bigfoot.com on Tue, Apr 24, 2001 at 06:01:05PM -0700

On Tue, Apr 24, 2001 at 06:01:05PM -0700, Tim Moore wrote:

> rtsp://rm.on24.com/media/news/04192001/palumbo_ted6.rm
> --stop--
> http://rm.on24.com/media/news/04192001/palumbo_ted6.rm

Hmm, the rtsp: fails while the http: works for that one. But then a tcp
connection doesn't depend on the realaudio masq module.

> Try '# strace /usr/bin/X11/realplay On24ram.asp > log' and see where the
> connect fails if you aren't getting specific error messages.

Unfortunately this spits out a bunch of stuff and then totally freezes up my
KDE 2.1.1 desktop. Probably totally unrelated, but that's what happens - the
part of the log that ends up in the frozen display doesn't tell me much, and
have to go to shell and kill strace to unfreeze things.

Could the problem be that I have realplay 8.0.3.412 on the systems here and
they've introduced some bug or incompatibility?

Whit



  reply	other threads:[~2001-04-25 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-25  1:14 2.2.19 Realaudio masq problem Whit Blauvelt
2001-04-25  1:01 ` Tim Moore
2001-04-25 18:38   ` Whit Blauvelt [this message]
2001-04-25 18:52     ` Dave Mielke
2001-04-25 20:56       ` Xavier Bestel
2001-04-25 23:12         ` Whit Blauvelt
2001-04-26  5:26           ` Xavier Bestel

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=20010425133804.A1094@free.transpect.com \
    --to=whit@transpect.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timothymoore@bigfoot.com \
    /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