Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Filip Peters <filip.peters@metris.be>
To: linux-sound@vger.kernel.org
Subject: Re: 2.2.0 oddities
Date: Fri, 05 Feb 1999 20:54:58 +0000	[thread overview]
Message-ID: <marc-linux-sound-91824849412883@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91821737719852@msgid-missing>

Florin,

Second question is easy, it's because you use zipped skins. There is a bug in x11amp that
shows up in the new kernel, the solution  is to unzip the skins or to not use them.

I had these error messages also for a while, the answer was on the kernel mailing list.
Hope this helps,

Filip.

Florin Andrei wrote:

>         I just compiled kernel-2.2.0 on a stock Red Hat 5.2 Intel box and saw few
> strange things:

> .....

>         2. I cannot use WinAmp anymore! It dies instantly, and reports "Whoops... You
> caught a bug...", preceded by "socket: Too many open files".

--
Filip Peters
fp@metris.be

      reply	other threads:[~1999-02-05 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-05 12:15 2.2.0 oddities Florin Andrei
1999-02-05 20:54 ` Filip Peters [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=marc-linux-sound-91824849412883@msgid-missing \
    --to=filip.peters@metris.be \
    --cc=linux-sound@vger.kernel.org \
    /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