Issue410993
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2001-03-24 10:39 by jafo, last changed 2022-04-10 16:03 by admin. This issue is now closed.
Messages (8) | |||
---|---|---|---|
msg4031 - (view) | Author: Sean Reifschneider (jafo) * | Date: 2001-03-24 10:39 | |
Picked up 2.1b2 and did "./configure" and "make test" on a RedHat 7.0-based system: test test_linuxaudiodev crashed -- linuxaudiodev.error: (11, 'Resource temporarily unavailable') Was running build as root, and "mpg123" runs successfully before and after. This is on a ThinkPad 240 with esssolo1 driver with 2.2.18 kernel. Sean |
|||
msg4032 - (view) | Author: Jeremy Hylton (jhylton) | Date: 2001-04-11 14:19 | |
Logged In: YES user_id=31392 I think we should report this failure as "test skipped." I think it would be essentially correct: The test was skipped because the device was in use. It's not a crash. Not sure how this test is affected by the recent changes to the module to handle EAGAIN. Sean or Guido-- can you try it with the updated module? My Linux audio config is screwed up. |
|||
msg4033 - (view) | Author: Guido van Rossum (gvanrossum) * | Date: 2001-04-11 16:36 | |
Logged In: YES user_id=6380 I think you misread his comment. He wasn't mpg123 *during* the test, he ran it before and after the test to verify that in fact his audio was in good working order. But, I do suggest to him to try the CVS version, which is one (relevant) fix ahead of 2.1b2. That version passes the test for me, but I don't hear a thing, so I'm not sure what's going on... |
|||
msg4034 - (view) | Author: Guido van Rossum (gvanrossum) * | Date: 2001-08-11 04:27 | |
Logged In: YES user_id=6380 We've gone back and forth over this one. It seems to happen for certain drivers for certain audio cards -- the problem has disappeared for most folks, but still works for some hardware (e.g. some Dell laptops running Mandrake). I've assigned this to Charles Waldman since he seems to know this area; he commented in python-dev that the initialization order is invalid. Charles if you still feel you won't touch this module (because you'd rather give us a new module that does the right thing), please close it as Won't Fix -- that's what I almost did until I remembered your interest. |
|||
msg4035 - (view) | Author: Guido van Rossum (gvanrossum) * | Date: 2001-09-05 17:56 | |
Logged In: YES user_id=6380 Charles, are you still interested in tackling this bug? If not, let us know! |
|||
msg4036 - (view) | Author: Charles G Waldman (cgw) | Date: 2001-09-05 18:36 | |
Logged In: YES user_id=7151 I've been out of town and somewhat out of the loop. But I'm back now. I will look into this over the weekend. |
|||
msg4037 - (view) | Author: Charles G Waldman (cgw) | Date: 2001-12-06 20:43 | |
Logged In: YES user_id=7151 Please see patch #489989 and the comments attached there. I have submitted a patch with the minimal fix. The reason this took so long was that I started working on a complete replacement for the audio output modules, which would detect ALSA/OSS/esd/etc, then I discovered the "libao" audio output library which does this. I think that any future work on an audio module for Python should just wrap libao. Patch 489989 can't do any harm, and it might help. |
|||
msg4038 - (view) | Author: Neil Schemenauer (nascheme) * | Date: 2002-03-22 18:50 | |
Logged In: YES user_id=35752 Patch 489989 has already been checked in and should have fixed this bug. I'm going to close it. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-10 16:03:53 | admin | set | github: 34225 |
2001-03-24 10:39:45 | jafo | create |