[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> Sometime ago I reported a bug in the arts driver, crashing on program
> exit. After some discussion, Eric applied a patch (thanks!). I'm sorry I
> couldn't comment on it at the time, but from what we gathered before, it
> should work.
Thanks for the confirmation.
> I didn't test it because at the time I was away from the computer and
> later upgraded kde to 3.2.x. The problem is that with KDE 3.2.x, the
> arts driver crashes directly in install_sound(). It seems the new
> versions of Arts introduced a bug where its C api can't be initialized
> more than once (even if you de-initialize it). Now install_sound asks
> all the allegro drivers wether they are available before chosing one,
> and with the arts C api the detection is to try to initialize arts. So
> the probe-then-really-install mechanism triggers arts' bug.
Thanks for the information. Very, very nice ;-)
> I can't see any easy way out of this. One would be to rewrite the driver
> with the C++ API to arts, bound to be better supported. But I don't
> think it's worth the trouble (how many people do use the allegro arts
> driver anyway?). I'll probably try to report the bug to the arts
> developpers. I personnaly decided it would be easier to get Alsa and
> dmix working on my system, but more on that in another mail.
Are you somewhat fluent in autoconf? It would be nice to have an autoconf
check that, upon detecting the buggy driver, automatically disables the
Allegro driver.
--
Eric Botcazou