RE: [pygame] [FYI] Pygame + Recent Linux Kernel Updates + ALSA

[Chris Ashurst <CAshurst@xxxxxxxx>]

Whoops...

Kernel: 2.6.20-16-generic
ALSA: 1.0.13 (and ALSA-OSS Bridge 1.0.12)
Sound Card: Creative Labs SB Audigy LS (CA0106) - Although the problem is
device independent
SDL: 1.2.11
Pygame: 1.7.1release-4.1 (although any pygame that makes a call to
pygame.mixer.init() explicitly or implicitly through pygame.init() will be
enough to trigger the issue)

Like I say, it could have affected a lot of people, or it *could* just be
me, but I'm just throwing it out there in case someone is banging their head
against a wall wondering why their pygame app refuses to start up and gives
no errors :)

-----Original Message-----
From: owner-pygame-users@xxxxxxxx [mailto:owner-pygame-users@xxxxxxxx]On
Behalf Of James Paige
Sent: Tuesday, June 19, 2007 11:07
To: pygame-users@xxxxxxxx
Subject: Re: [pygame] [FYI] Pygame + Recent Linux Kernel Updates + ALSA


On Tue, Jun 19, 2007 at 08:45:57AM -0400, Chris Ashurst wrote:
> Not sure how many people this may have affected (if any at all), but if
any
> of you develop with pygame in a *nix environment and have recently
performed
> a kernel update and found pygame not getting anywhere past pygame.init(),
> it's because of ALSA locking up whenever it is called by any software that
> uses it.
> 
> ...

What kernel version?
What ALSA version (if installed separately)?
What sound card?
What SDL version?
What pygame version?

---
James Paige




CONFIDENTIAL NOTICE: This email including any attachments, contains 
confidential information belonging to the sender. It may also be 
privileged or otherwise protected by work product immunity or other 
legal rules. This information is intended only for the use of the 
individual or entity named above.  If you are not the intended 
recipient, you are hereby notified that any disclosure, copying, 
distribution or the taking of any action in reliance on the contents 
of this emailed information is strictly prohibited.  If you have 
received this email in error, please immediately notify us by 
reply email of the error and then delete this email immediately.